|
Power state |
Additional
transition energy |
|
|
Category 1 |
Category 2 |
|
|
Deep sleep |
|
|
|
Light sleep |
90 |
1088 |
Please refer to RP-220297 for detailed scope of the SI.
R1-2204919 Work plan for NR network energy savings Huawei
R1-2203947 TR 38.864 skeleton for study on network energy savings for NR Huawei
[109-e-R18-NW_ES-01] – Yi (Huawei)
Email discussion and approval of TR skeleton for Rel-18 SI on network energy savings for NR by May 13
R1-2205307 TR 38.864 skeleton for study on network energy savings for NR Rapporteur (Huawei)
Decision: As per email decision posted on May 12th,
TR skeleton for TR 38.864 Study on network energy savings for NR is endorsed.TR 38.864 is endorsed as v0.0.2 in R1-2205694 as basis for further updates.
Including evaluation methodology, base station energy consumption model, KPIs, and evaluation results.
R1-2204881 Modeling and evaluation methodology for network energy saving Ericsson
o FFS: If and how the maximum output power scales the active transmission power consumption.
Decision: The document is noted.
R1-2203172 Discussion on performance evaluation for network energy saving Huawei, HiSilicon
R1-2203224 NW energy savings performance evaluation Nokia, Nokia Shanghai Bell
R1-2203341 Discussion on performance evaluation of network energy savings Spreadtrum Communications
R1-2203481 Evaluation Methodology and Power Model for Network Energy Saving CATT
R1-2203575 Discussions on NW energy savings performance evaluation vivo
R1-2205178 Discussion on NW energy saving performance evaluation ZTE, Sanechips (rev of R1-2203603)
R1-2203662 Discussion on network energy saving performance evaluation methods China Telecom
R1-2203830 Discussions on performance evaluation of network energy saving xiaomi
R1-2203919 NW energy savings performance evaluation Samsung
R1-2204073 On network energy savings evaluation methodology and power model Panasonic
R1-2204100 Base station energy consumption model, evaluation methodology, and KPIs for network energy saving FUTUREWEI
R1-2204256 On NW energy savings performance evaluation Apple
R1-2204318 Discussion on network energy saving performance evaluation CMCC
R1-2204391 Discussion on NW energy savings performance evaluation NTT DOCOMO, INC.
R1-2204628 Discussion on performance evaluation for network energy savings LG Electronics
R1-2204686 NW energy savings performance evaluation MediaTek Inc.
R1-2204811 Discussion on Network Energy Saving Evaluations Intel Corporation
R1-2204831 Performance evaluation for network energy saving InterDigital, Inc.
R1-2205045 NW energy savings performance evaluation Qualcomm Incorporated
R1-2205083 Initial views on NW energy savings performance evaluation Fujitsu Limited
[109-e-R18-NW_ES-02] – Yi (Huawei)
Email discussion on performance evaluation by May 20
- Check points: May 12, May 18, May 20
R1-2205308 FL summary#1 for performance evaluation for NR NW energy savings Moderator (Huawei)
From May 13th GTW session
Agreement
For evaluation purpose, the energy consumption modeling for a BS includes at least the following:
· Reference configuration
o FFS other details
o Note FR1 and FR2 to be separately considered for detailed parameters
· Multiple power state(s) including sleep/non-sleep mode(s) with relative power, and associated transition time/energy
· Scaling method to be applied at least for non-sleep mode.
o FFS other details including scaling for sleep mode
R1-2205402 FL summary#2 for performance evaluation for NR NW energy savings Moderator (Huawei)
From May 17th GTW session
Agreement
For evaluation purpose, the BS energy consumption model should at least include the power consumption of BS on slot-level.
· Note that symbol-level power consumption to reflect different BW (or RB utilization) / time-occupancy / tx-rx direction of different symbols in a slot is considered.
o FFS details (e.g. explicit symbol-level power modelling, scaling slot-level power to symbol level power for various cases, etc.)
o Note: system simulation evaluations can be per slot regardless of detailed approach for calculating symbol-level power consumption.
Agreement
·
For evaluation, at least
for non-sleep mode and TDD, the BS power consumption for DL and UL are
separately modelled, allowing DL-only transmission or UL-only reception.
o FFS: whether UL-only reception energy consumption model can be derived/simplified from DL-only transmission energy consumption model
· FFS: the impact of UL reception and/or DL transmission on sleep modes and associated transition time/energy
· FFS: whether/how to define an idle state, where BS is neither transmitting nor receiving but also doesn’t enter into any sleep mode or define it as sleep mode
· FFS: whether the model for FDD can be based on the model for TDD
Agreement
· For evaluation purpose,
o Study how to define sleep modes and determine the characteristics for each mode from one or multiple of the below
§ Relative power
§ Transition time
§ Transition energy
§ Other approaches are not precluded
§ Note: BS components that can be turned off can be considered for discussion purpose when defining the specific values of the characteristics for sleep modes.
o Study whether sleep mode is defined for DL(TX) and UL(RX) jointly or separately
o Study the assumption of order for BS entering/resuming from a sleep mode to another mode (sleep or non-sleep) and the associated transition time and energy, i.e. state machine which may have impact on the transition energy.
Agreement
· For evaluation, the scaling in a BS energy consumption model can be considered based on one or more of the following,
o Number of used physical antenna elements, or TX/RX chains
§ FFS: Mapping between used TX/RX chains and used antenna ports
§ FFS: Mapping between physical antenna elements and TX/RX chains
o Occupied BW/RBs for DL and/or UL in a slot/symbol in one CC
o number of CCs in CA
§ FFS dependency of RF sharing
o number of TRPs
o PSD or transmit power
§ FFS dependency on BW scaling
§ FFS: PA energy efficiency value
o number of DL and/or UL symbols occupied within a slot
o FFS other domain scaling
o FFS scaling is linearly or else, for each domain
· Above does not necessarily imply that BS energy consumption model that takes into account all listed scaling factors will be developed
Decision: As per email decision posted on May 19th,
Agreement
For BS energy consumption evaluation, in addition to the energy saving gain,
· At least UPT/UE power consumption/access delay/latency should be considered for performance impact evaluation
· Note: this doesn’t necessarily mean that all the above are considered for all evaluation results. However, multiple KPIs are expected to be evaluated for a given technique. And this does not preclude to consider other KPIs when found appropriate for certain techniques/scenarios.
Agreement
At least urban macro is prioritized for FR1. FFS the baseline deployment assumption for FR2.
Agreement
· FTP3 (0.5MB as packet size, 200ms as mean inter-arrival time), FTP3 IM (0.1MB as packet size, 2s as mean inter-arrival time) and VOIP can be considered in the evaluation
· FFS: with possible further prioritization, different model between DL and UL, and/or other traffic models that can be optionally considered.
FFS associated scenarios/configurations, e.g. C-DRX.
R1-2205468 FL summary#3 for performance evaluation for NR NW energy savings Moderator (Huawei)
From May 19th GTW session
Agreement (further updated as shown in red – May 20th post)
For evaluation and BS
energy consumption modeling purpose, forFor single CC case, at least the following in table should be
considered for reference configuration
o Note: other TX-RX RU number and corresponding BS antenna configuration can be considered in SLS assumptions
|
|
Set 1 FR1 |
Set 2 FR1 |
Set 3 FR2 |
|
Duplex |
TDD |
FDD |
TDD |
|
System BW |
100 MHz |
20 MHz |
100 MHz |
|
SCS |
30 kHz |
15 kHz |
120 kHz |
|
Number of TRP |
1 |
1 |
1 |
|
Total number of DL TX RUs |
64 |
(working assumption) 32 |
2 |
|
Total DL power level |
55dBm |
[49dBm] – to be further discussed and finalized in future meetings |
43dBm – to be further discussed and finalized in future meetings
EIRP limited to 78dBm – to be further discussed and finalized in future meetings |
|
Total number of UL Rx RUs |
64 |
(working assumption) 32 |
2 |
Decision: As per email decision posted on May 20th,
Agreement
As a starting point,
· macro cell BS for FR1 is assumed for energy consumption model.
· FFS: micro cell BS for FR2 is assumed for energy consumption model.
Agreement
The evaluation baseline for energy saving study/evaluation for BS includes at least NR R15 mandatory without capability features. Optional features from R15 onwards (e.g. CA, MIMO) as well as implementation-based energy saving techniques should be explicitly reported and described if used in the evaluation baseline.
· FFS: need of alignment for certain configurations/implementation-based schemes.
Decision: As per email decision posted on May 21st,
Agreement
· Similar to UE power saving study, percentage of energy consumption reduction from the baseline is used to express BS energy saving gain.
· SLS is considered as baseline evaluation method. Other method, including numerical analysis and LLS can also be considered. At least one of the methods should be selected and used for evaluation of a specific technique (selection and criteria is up to proponent).
Working assumption
For evaluation, for energy consumption modelling for FDD and the case of simultaneous DL transmission and UL reception for non-sleep mode, study the following with potential down-selection in RAN1#110
· Option 1: the power consumption is the total of DL and UL power consumption
· Option 2: the power consumption for UL is neglected
· Other option is not precluded
· Note the DL (or UL) power consumption can be obtained using a same approach as that obtained from the DL (or UL)-only in TDD model
Final summary in R1-2205551.
R1-2203173 Discussion on network energy saving techniques Huawei, HiSilicon
· Proposal 1: Study possible methods to optimize/simplify the transmission of common signals, e.g. SSB and SIB1, in single-carrier and multi-carrier scenarios with minimum extra access delay to NR and/or in NR co-existing with LTE.
· Proposal 2: Study whether additional spec effort is required, in the case UE DRX is already configured.
· Proposal 3: Study dynamic TRX muting/power adjustment, e.g. in dynamic-level, with proper UE feedback/assistance information, e.g. enhanced CSI measurement/report.
Decision: The document is noted.
R1-2204319 Discussion on network energy saving techniques CMCC
· Proposal 1: The measurement impacts due to TRX on/off can be studied in Rel-18, including CSI-RS measurement, PL RS measurement, beam failure recovery, radio link monitoring, cell selection, and CSI feedback.
· Proposal 2: CSI-RS adaptation for network energy saving can be studied.
· Proposal 3: SRS, PRACH, or SR can be considered as a starting point for wake-up signal design, SR or CSI reporting enhancement can be considered for assistance information feedback.
· Proposal 4: The following three alternatives for time and frequency domain power saving enhancements can be further studied,
o No transmission of SSB/SIB in the carrier
o Increased SSB/SIB transmission period
o On demand SSB/SIB transmission
· Proposal 5: gNB DTX can be studied to help network power saving.
· Proposal 6: When period transmission behavior of SSB/SIB is changed, the impact on legacy UEs needs to be considered, including the initial access performance, measurement performance, etc.
Decision: The document is noted.
R1-2203225 Network energy saving techniques Nokia, Nokia Shanghai Bell
R1-2203342 Discussion on network energy saving techniques Spreadtrum Communications
R1-2203482 Network Energy Saving techniques in time, frequency, and spatial domain CATT
R1-2203576 Discussions on network energy saving techniques vivo
R1-2203604 Discussion on NW energy saving techniques ZTE, Sanechips
R1-2203636 On Network Energy Saving Techniques Fraunhofer IIS, Fraunhofer HHI
R1-2203663 Discussion on network energy saving techniques China Telecom
R1-2203831 Discussions on techniques for network energy saving xiaomi
R1-2203920 Network energy saving techniques Samsung
R1-2203936 Discussion on network energy saving techniques NEC
R1-2204010 Study on network energy saving techniques OPPO
R1-2204043 Discussion on network energy saving techniques CENC
R1-2204074 Discussion on potential network energy saving techniques Panasonic
R1-2204101 Potential enhancements for network energy saving FUTUREWEI
R1-2204257 Discussion on Network energy saving techniques Apple
R1-2204392 Discussion on NW energy saving techniques NTT DOCOMO, INC.
R1-2204424 Network energy saving techniques Lenovo
R1-2204443 Study on potential L1 network energy saving techniques for NR ITRI
R1-2204629 Discussion on physical layer techniques for network energy savings LG Electronics
R1-2204687 Network energy saving techniques MediaTek Inc.
R1-2204756 Discussion on Network energy saving techniques CEWiT
R1-2204812 Discussion on Network Energy Saving Techniques Intel Corporation
R1-2204832 Potential techniques for network energy saving InterDigital, Inc.
R1-2204882 Network energy saving techniques Ericsson
R1-2205046 Network energy saving techniques Qualcomm Incorporated
R1-2205070 Potential Techniques of Network Energy Savings Rakuten Mobile
R1-2205084 Initial views on network energy saving techniques Fujitsu Limited
R1-2205140 Discussion Summary for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
[109-e-R18-NW_ES-03] – Daewon (Intel)
Email discussion on NW energy saving techniques by May 20
- Check points: May 13, May 20
R1-2205141 Summary #1 for email discussion on energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
R1-2205533 Summary #2 for email discussion on energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
Decision: As per email decision posted on May 20th,
Agreement
Further study techniques and enhancements for increasing time domain energy saving opportunities by the gNB, including (but not limited to) the following aspects:
· potential methods of reducing/adapting transmission/reception of common channels/signals, e.g. SSB, SIB1, other SI, paging, PRACH, and its impact to initial access procedure, cell (re)selection, handover, synchronization and measurements performed by the idle/inactive/connected UE;
o potential methods of reducing transmission/reception of common channels/signals can include no- or reduced-transmission/reception, increased periodicity, enablement of on-demand transmission/reception of common channels/signals, or offloading of common channels/signals to other carriers or use of light or relaxed versions of common channels /signals
· potential methods of reducing/adapting transmission/reception of periodic and semi-persistent signals and channels configuration such as CSI-RS, group-common/UE-specific PDCCH, SPS PDSCH, PUCCH carrying SR, PUCCH/PUSCH carrying CSI reports, PUCCH carrying HARQ-ACK for SPS, CG-PUSCH, SRS, positioning RS (PRS), etc.
· semi-static and/or dynamic cell on/off in one or more granularity, e.g. /subframe/slot/symbol; some examples are:
o Cell/network node activation request by the UE, for example using signal/channel from UE for gNB’s wake-up request
o enhancements to L1/L2 based mobility to efficiently enable a network node (e.g. TRP, repeater) on/off operation within a cell (within network energy saving SI scope)
o signaling enhancements for indication of semi-static and/or dynamic cell/subframe/slot/symbol on/off duration
· support of periodic and/or on-demand reference signal(s) from the gNB to aid discovery of a cell;
· dynamic adaptation of UE C-DRX configurations in a UE-group or cell-specific manner
· Mechanism to utilize potential energy saving states or sleep modes and the transition between states from leveraging cell on/off opportunities
o including studies of waking up gNB due to user traffic, or user density, or gNB receiving wake up signal
o including technique to allow discovery and measurement of cells in sleep or dormant states
· UE assistant information facilitating BS time domain adaptation
Note: For all techniques above, study of time domain techniques is applicable for single component carrier and multi-component carrier cases. Use of UE grouping and its interaction with proposed techniques can be considered.
Agreement
Further study techniques and enhancements for frequency resource usage adaptation by the gNB, including (but not limited to) the following aspects:
· For operations with single-carrier or within a single CC
o Enhancements to dynamic bandwidth adaptation
§ including adjustments to RBs and/or BWP used by (Rel-18) UEs for transmission and reception, reducing BWP switch delay, UE-group BWP switching, and joint adaptation of transmission bandwidth and power spectral density
o supporting UE group-common BWP or cell-specific BWP or dedicated BWP for network energy savings, and related BWP switching mechanism
o Enhancements for the case of frequent BWP switching such as resource configurations for SPS PDSCH and Type-2 CG PUSCH
· For operation with multi-carrier
o enablement of reducing/adapting common channels/signals for some CC in multi-carrier operations
§ including enablement of SSB-less secondary cell operation for some CC in case of inter-band CA. For SSB-less cell operation enablement, study the conditions and restrictions required for the operation and the related procedures for idle/inactive/connected UEs including SCell activation procedure with potential RAN4 involvement
§ including enablement of SIB-less operation for some CC in case of intra-band and inter-band CA.
§ Reducing/adapting gNB’s transmission/reception of other common channels/signals (than SSB) and TRS for some CC in multi-carrier operations
o enhancements on Scell activation and deactivation, enhancements on Scell dormancy and dynamic Pcell switching
§ including triggering conditions and methods for signaling activation/deactivation
§ including UE group common dynamic Pcell switching
Agreement
Further study techniques and enhancements for the adaptation of number of spatial elements of the gNB, including (but not limited to) the following aspects:
· Note: spatial elements may include antenna element(s), TxRU(s) (with sub-array/full-connection), antenna panel(s), TRxP(s) (co-located or geographically separated from each other), logical antenna port(s) (corresponding to specific signals and channels)
· impact to UE operations from dynamic adaptation of spatial elements, e.g. measurements, CSI feedback, power control, PUSCH/PDSCH repetition, SRS transmission, TCI configuration, beam management, beam failure recovery, radio link monitoring, cell (re)selection, handover, initial access, etc.,
· feedback/assistance information from the UE required for support dynamic spatial element adaptation
o for example, CSI measurement and reports, SR, etc
· signaling methods, including reduced signaling, for enabling dynamic spatial element adaptation
· for example, group-common L1 signaling, broadcast signaling, MAC CE, etc.
· dynamic TRxP adaptation;
o study of triggering on/off conditions for TRxP(s)
§ note this may not have specification impact and could potentially be up to network implementation.
o study of SSB, PL-RS, TRS, and CSI-RS re-configuration and its impact to initial access procedure, synchronization and measurements performed by the idle/inactive/connected UE
· dynamic logical port adaptation and efficient port reconfigurations
o study details of signaling the port (e.g. NZP CSI-RS ports) (if required to be known by the UE)
o study dynamic adaptation (including activation/deactivation) of CSI measurement or report configuration for port adaptation
· Joint adaptation of spatial-domain, frequency-domain and/or power-domain configurations to avoid coverage loss
· grouping of UEs to reduce transmission and reception footprint at the gNB; including but not limited to the following
o grouping of users in spatial domain
Agreement
Further study the necessity of RAN1 change for techniques and enhancements for adaptation of transmission power/processing and/or reception processing of signals/channels by the gNB, including (but not limited to) the following aspects:
· dynamic adjustment of transmission power
o including which signals/channels the adaptation of transmission power should be applicable for. For example, dynamic DL power control for specific channel / reference signal, such as CSI-RS, adjustment of maximum PSD assigned to PRBs of PDSCH, etc.
o studying potential UE feedback/assistance information for adjustment of transmission power
o studying PA efficiency improvements to maintain transmission quality (e.g., EVM) when operating at higher efficiency, potentially with RAN4 involvement
o studying geographical area/user density to adjust the transmission power
· adaptation of gNB transceiver algorithms and processes to improve power efficiency:
o including techniques aided by UE, e.g., utilizing legacy or enhanced feedback mechanism;
o for example, adaptation of digital pre-distortion (DPD), use of digital post distortion (for improving power efficiency) by the UE, adaptation to transceiver filtering operation
o impact to UE implementation and power consumption should be considered
· tone reservation techniques (to improve PAPR and power efficiency);
o It is noted that tone reservation techniques for UE will be studied in Rel-18 further NR coverage enhancement WI, as indicated in RP-213579
Agreement
Further study techniques and enhancements on assistance information from the UE to aid the gNB to perform energy saving techniques
· Some examples of assistance information are, but not limited to:
o preferred SSB configurations,
o indication of semi-static UL channel transmissions,
o indication of UE’s buffer status for UL channel transmissions,
o UE traffic information such as service priority, delay tolerance, data rate, data volume, traffic type, time criticality, and packet size(s),
o coverage, mobility status, location.
o conditions for triggering the assistance information from the UE
Final summary in R1-2205554.
R1-2203226 Others Nokia, Nokia Shanghai Bell
R1-2205160 Evaluation results of network energy saving CATT (rev of R1-2203483)
R1-2205175 Initial evaluation results for network energy saving scheme vivo (rev of R1-2203577)
R1-2203605 Consideration about NW energy saving ZTE, Sanechips
R1-2204320 Discussion on network energy saving scheme in deployment CMCC
R1-2204883 Other aspects related to network energy saving Ericsson
R1-2204918 Discussion on information assistance for network energy saving Huawei, HiSilicon
Please refer to RP-221443 for detailed scope of the SI.
[110-R18-NW_ES] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Yi (Huawei)
R1-2207020 TR 38.864 v0.1.0 for study on network energy savings for NR Rapporteur (Huawei)
From AI 5
R1-2207999 LS on skeleton of TR 38.864 for NR network energy savings RAN3, Huawei
Including evaluation methodology, base station energy consumption model, KPIs, and evaluation results.
R1-2205755 BS Energy Consumption Model and Sleep States FUTUREWEI
R1-2205860 Discussion on performance evaluation for network energy saving Huawei, HiSilicon
R1-2205999 Discussion on performance evaluation of network energy savings Spreadtrum Communications
R1-2206053 Discussions on NW energy savings performance evaluations on vivo
R1-2206074 NW energy savings performance evaluation Nokia, Nokia Shanghai Bell
R1-2206141 On network energy savings evaluation methodology and power model Panasonic
R1-2206172 Discussion on NW energy savings performance evaluation Fujitsu
R1-2206411 Evaluation Methodology and Power Model for Network Energy Saving CATT
R1-2206665 Performance evaluation for network energy saving InterDigital, Inc.
R1-2206696 Discussion on BS energy saving model and evaluation China Telecom
R1-2206838 NW Energy Savings Performance Evaluation Samsung
R1-2206925 Discussion on network energy saving performance evaluation CMCC
R1-2206979 NW energy savings performance evaluation MediaTek Inc.
R1-2207037 Discussion on performance evaluation for network energy savings LG Electronics
R1-2207059 Discussion on NW energy saving performance evaluation ZTE, Sanechips
R1-2207079 Evaluation and power model for network energy savings Rakuten Mobile, Inc
R1-2207245 NW energy savings performance evaluation Qualcomm Incorporated
R1-2207343 On NW energy savings performance evaluation Apple
R1-2207418 Discussion on NW energy savings performance evaluation NTT DOCOMO, INC.
R1-2207437 Network energy consumption modeling and evaluation Ericsson
R1-2207694 Discussion on Network energy saving performance evaluations Intel Corporation (rev of R1-2206595)
R1-2207685 Discussion on NW energy savings performance evaluation OPPO (rev of R1-2206308)
R1-2207910 FL summary#1 for EVM for NR NW energy savings Moderator (Huawei)
From Tuesday session
Agreement
For non-sleep mode, the relative power value in power model table for UL reception and/or DL transmission is provided based on reference configuration.
Agreement
For set 2 FR1 FDD TxRx reference configuration, confirm the WA as 32 in reference configuration.
Agreement
The total DL power level is 49 dBm for set 2 FR1 FDD reference configuration.
R1-2207987 FL summary#2 for EVM for NR NW energy savings Moderator (Huawei)
R1-2208216 FL summary#3 for EVM for NR NW energy savings Moderator (Huawei)
Agreement
For the purpose of evaluation, adopt the following as BS power consumption model. These entries for this table is per reference configuration set.
· FFS: One or multiple values for relative power and transition time.
|
Power state |
Characteristic |
Relative Power |
Additional transition energy3 |
Total transition time |
|
Deep sleep1 |
There is neither DL transmission nor UL reception. Time interval for the sleep should be larger than the total transition time entering and leaving this state. |
P1=1 |
E1 |
T1 |
|
Light sleep |
There is neither DL transmission nor UL reception. Time interval for the sleep should be larger than the total transition time entering and leaving this state. (P2>P1) |
P2 |
E2 |
T2 |
|
Micro sleep |
There is neither DL transmission nor UL reception. Immediate transition is assumed for network energy saving study purpose from or to a non-sleep state. |
P3 |
0 |
0 |
|
Active DL |
There is only DL transmission. |
P4 |
NA |
NA |
|
Active UL |
There is only UL reception.
|
P5 |
NA |
NA |
|
Note 1: Depending on implementations, there could be a state that the power is lower than deep sleep and requires larger total transition time, e.g. hibernating sleep or Quasi-off, which is not explicitly modeled in this study for evaluation purpose. Note 3: Unit in relative power times duration. FFS: Details on how transition energy is defined. |
||||
· For simultaneous DL and UL transmission for FDD, the power for UL reception is neglected in this study.
· FFS: Optionally, a state machine where BS may transit between sleep modes without entering non-sleep mode can be considered. Companies are to report the involved sleep modes and the assumptions for inter-sleep mode transition time used in their evaluations.
· FFS: Details on how to use the above table for low power uplink reception (e.g. for WUS).
Working Assumption
For reference configuration set 1, the values are provided as below. FFS set2 and set 3.
|
Power state |
Relative Power P |
Total transition time T |
||
|
Deep sleep |
1 |
1 |
Cat 1:
50ms |
Cat 2:
10s |
|
Light sleep |
Cat 1: 25 |
Cat 2: 2.1 |
Cat 1: 6 ms |
Cat 2: 640 ms |
|
Micro sleep |
Cat1: 55 |
Cat 2: 5.5 |
0 |
0 |
|
Active DL |
Cat 1: 280 |
Cat 2: 32 |
N.A. |
N.A. |
|
Active UL |
Cat 1: 110 |
Cat 2: 6.5 |
N.A. |
N.A. |
Agreement
For evaluation purpose,
· a load (L) of a cell is a percentage of resources used for UE specific PDSCH / PUSCH
· The following load scenarios are considered
|
Load scenario |
Characteristics |
|
Idle/empty load |
· Include cell-specific signals and channels, and · L = 0 |
|
low load |
· Include cell-specific signals and channels, and · 0 < L≤15 |
|
Light load |
· Include cell-specific signals and channels, and ·
0 < L≤ |
|
Medium load |
· Include cell-specific signals and channels, and ·
|
|
For CA, the companies report whether the load is defined per CC or across all CCs. |
|
Agreement
· For FR1, urban micro can be optionally considered.
· For FR2, urban micro is prioritized, with ISD=200 m is assumed.
Agreement
It is up to company report which traffic model is used among the agreed three traffic models in their evaluations.
· Other models may be used as well. Parameter (e.g. packet size and arrival rate) adjustment can be optionally considered and reported.
Agreement
For set 3 FR2 reference configuration, the total DL power level and EIRP limit is set as 33 dBm and 63 dBm respectively. Note EIRP limit is also scaled with the number of TxRU.
Agreement
For evaluation purpose, network energy saving gain is computed based on the energy consumptions for a technique and the baseline over the same duration.
See post-meeting decisions under Annex F.
R1-2205756 Enhancements for network energy saving FUTUREWEI
R1-2205861 Discussion on network energy saving techniques Huawei, HiSilicon
R1-2206000 Discussion on network energy saving techniques Spreadtrum Communications
R1-2206054 Discussions on network energy saving techniques vivo
R1-2206075 Network energy saving techniques Nokia, Nokia Shanghai Bell
R1-2206142 Discussion on potential network energy saving techniques Panasonic
R1-2206173 Discussion on Network energy saving techniques Fujitsu
R1-2206242 Discussion on network energy saving techniques NEC
R1-2206309 Discussion on network energy saving techniques OPPO
R1-2206412 Network Energy Saving techniques in time, frequency, and spatial domain CATT
R1-2206517 Network energy saving techniques Lenovo
R1-2206596 Discussion on Network energy saving techniques Intel Corporation
R1-2206655 Discussions on techniques for network energy saving Xiaomi
R1-2206666 Potential techniques for network energy saving InterDigital, Inc.
R1-2206697 Discussion on potential techniques for network energy saving China Telecom
R1-2206839 Network energy saving techniques Samsung
R1-2206926 Discussion on network energy saving techniques CMCC
R1-2206947 On Network Energy Saving Techniques Fraunhofer IIS, Fraunhofer HHI
R1-2206980 Network energy saving techniques MediaTek Inc.
R1-2207038 Discussion on physical layer techniques for network energy savings LG Electronics
R1-2207060 Discussion on NW energy saving techniques ZTE, Sanechips
R1-2207074 Discussion on Network energy saving techniques CEWiT
R1-2207119 Discussion on network energy saving techniques Rakuten Mobile, Inc
R1-2207246 Network energy saving techniques Qualcomm Incorporated
R1-2207344 Discussion on Network energy saving techniques Apple
R1-2207419 Discussion on NW energy saving techniques NTT DOCOMO, INC.
R1-2207438 Network energy savings techniques Ericsson
R1-2207446 Discussion on potential L1 network energy saving techniques for NR ITRI
R1-2207481 Discussion on network energy saving techniques KT Corp.
R1-2207841 Discussion Summary#1 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
R1-2208185 Discussion Summary#2 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
For future meetings:
Please refer to RP-221443 for detailed scope of the SI.
[110bis-e-R18-NW_ES-03] – Yi (Huawei)
TR update endorsement by October 12
R1-2209679 TR 38.864 v0.2.0 for study on network energy savings for NR Huawei
Decision: As per email decision posted on Oct 13th, R1-2209679 is endorsed in principle. An updated version is expected for the inclusion of the outcome of RAN1#110bis-e. To be achieved via post-RAN1#110bis-e email discussion.
R1-2210593 Comment collection for draftTR 38.864 Moderator (Huawei)
Including evaluation methodology, base station energy consumption model, KPIs, and evaluation results.
R1-2208381 BS Sleep States FUTUREWEI
R1-2208424 Discussion on performance evaluation for network energy saving Huawei, HiSilicon
R1-2208518 NW energy savings performance evaluation Nokia, Nokia Shanghai Bell
R1-2208561 Discussion on performance evaluation of network energy savings Spreadtrum Communications
R1-2208654 Discussion on NW energy savings performance evaluation vivo
R1-2208776 Discussion on network energy saving performance evaluation methods China Telecom
R1-2208832 Discussion on NW energy savings performance evaluation OPPO
R1-2208987 Evaluation Methodology and Power Model for Network Energy Saving CATT
R1-2209022 Discussion on NW energy savings performance evaluation Fujitsu
R1-2209063 Discussion on Network energy saving performance evaluations Intel Corporation
R1-2209195 Discussion on NW energy saving performance evaluation ZTE, Sanechips
R1-2209348 Discussion on network energy saving performance evaluation CMCC
R1-2209452 Discussion on performance evaluation for network energy savings LG Electronics
R1-2210257 Network Energy Savings Performance Evaluation MediaTek Inc. (rev of R1-2210239, rev of R1-2209500)
R1-2209617 Discussion on network energy savings performance Rakuten Symphony
R1-2209653 Performance evaluation for network energy saving InterDigital, Inc.
R1-2209742 NW energy savings performance evaluation Samsung
R1-2209858 Network energy consumption modeling and evaluation Ericsson
R1-2209913 Discussion on NW energy savings performance evaluation NTT DOCOMO, INC.
R1-2209996 NW energy savings performance evaluation Qualcomm Incorporated
R1-2210021 Performance evaluation for network energy saving Lenovo
[110bis-e-R18-NW_ES-01] – Yi (Huawei)
Email discussion on performance evaluation by October 19
- Check points: October 14, October 19
R1-2210301 FL summary#1 for R18 NW_ES Moderator (Huawei)
From Oct 10th GTW session
For companies to consider when providing evaluation results:
· Use the following table with adding Category, as a draft template for collection of simulation results
· The template can be further adjusted with input when captured into TR.
· Other formats are not precluded.
|
Company |
NW energy saving scheme |
ES Gain |
ES gain for each configuration |
UPT
|
Other impact |
Evaluation methodology/baseline assumption |
Note |
|
|
|
Editor Note: includes a range for different configurations, if possible. |
Editor Note: include gain for each configuration, if possible. For example, per Load, configurations of common signals etc. |
Editor Note: may include average UPT, target UPT (95%/50%/5%) and UPT loss/gain per ES techniques. May also include scheduling latency, user plane latency etc.
|
Editor Note: may include coverage, UE power consumption, EE with definition, etc. |
Editor Note: may include selected parameters/baselines etc, if there are multiple. |
Editor Note: other important setting that needs to be reported, e.g. the selected options/approaches as mentioned in R1-2208654. |
R1-2210302 FL summary#2 for R18 NW_ES Moderator (Huawei)
From Oct 12th GTW session
Agreement:
Confirm the previous Working Assumption with the following update
· For RAN1 evaluation purpose, for reference configuration set 1/2/3, the values are provided as below.
· The transition time is confirmed without update.
· FFS: The time unit to be used when calculating the energy consumption
|
Power state |
Relative Power P for Category 1 |
Relative Power P for Category 2 |
||||
|
Set 1 |
Set 2 |
Set 3 |
Set 1 |
Set 2 |
Set 3 |
|
|
Deep sleep |
1 |
1 |
1 |
1 |
1 |
1 |
|
Light sleep |
25 |
|
|
2.1 |
|
|
|
Micro sleep |
55 |
50 |
38 |
5.5 |
5 |
3 |
|
Active DL |
280 |
|
152 |
32 |
|
|
|
Active UL |
110 |
90 |
80 |
6.5 |
5.8 |
4.2 |
Agreement:
· For set 1/2/3, the additional energy (unit in relative power*(duration in ms)) is
|
Power state |
Additional
transition energy |
|
|
Category 1 |
Category 2 |
|
|
Deep sleep |
|
|
|
Light sleep |
90 |
1088 |
R1-2210303 FL summary#3 for R18 NW_ES Moderator (Huawei)
Presented in Oct 17th GTW session
R1-2210592 FL summary#4 for R18 NW_ES Moderator (Huawei)
From Oct 19th GTW session
Agreement
Capture in TR that,
· The BS power model defined in this study is a simplified model for the purposes of evaluations, considering single-RAT NR BSs only. This does not mean a BS cannot benefit from the identified techniques when serving multi-RAT.
Transition among power states, transition time, are implementation specific, and different BS types may support a different number of power states with different characteristics, i.e., power consumption values and required transition time.
Agreement
All calculation of energy consumption should use the same time unit (companies to indicate which time unit they used).
Agreement
: a static part of power for BS in
active, which is not scaled based on reference configurations. 
: a dynamic part of power for BS in active, which is scaled
based on reference configuration.
, where 
, 
,
is the fraction of active TRxRUs, the ratio of RF bandwidth
and maximum system BW and the ratio of PSD per TxRU between the DL
transmission and reference configuration, respectively
is the power part related to PA.
is used for evaluation, =
for any sf, sp are used for evaluation, = 0.76 if 
; otherwise, 
: a static part of power for BS in
active, which is not scaled based on reference configurations. 
: a dynamic part of power for BS in active, which is scaled
based on reference configuration and is the percentage of active TRxRUs
when no scaling is applied (i.e. scaling factor is 1)
At least 
= 1 is supported. Additional one or
two more values are FFS.
Agreement
· For FR1 SLS assumptions, add parameters in the below table as additional SLS parameters.
|
|
|
Set 1 FR1 |
Set 2 FR1 |
|
1 |
Channel model |
3D-Uma as in TR 38.901 |
3D-Uma as in TR 38.901 |
|
2 |
percentage of high loss and low loss building type |
100% low loss |
100% low loss |
|
3 |
Guard band ratio on simulation bandwidth |
TDD: 2.08% (272 RB for 30kHz SCS and 100 MHz bandwidth) |
FDD: 6.4% (104RB for 15kHz SCS and 20 MHz BW) |
|
4 |
HARQ scheme |
Ideal |
Ideal |
|
5 |
Max HARQ retransmission |
3 |
3 |
|
6 |
Target BLER |
10% of first transmission |
10% of first transmission |
|
7 |
Power control parameters |
Open loop, P0=-80dBm, alpha=0.8 |
Open loop, P0=-80dBm, alpha=0.8 |
|
10 |
SS blocks per SSB burst |
Up
to 8 |
Up
to 4 |
|
11 |
SSB time resource |
4 symbols for each SSB |
4 symbols for each SSB |
|
12 |
SSB frequency resource |
20 RBs |
20 RBs |
· For (Set 3) FR2 SLS assumptions, use Table below as baseline assumptions
|
BS type |
Micro |
UE BWP |
100 Mhz |
|
Network layout and inter-site distance |
21 cells Wraparound (ISD=200m, as agreed) |
UE height |
1.5m |
|
Channel model |
UMi |
UE noise figure |
13 dB |
|
Link direction |
Downlink |
UE antenna element gain |
5 dBi |
|
Frequency range |
30GHz |
UE receiver |
MMSE-IRC |
|
Duplex |
TDD |
UE deployment |
20% Outdoor in cars: 30km/h, 80% Indoor in houses: 3km/h |
|
Frame structure |
DDDSU (S: 10D:2G:2U) |
Traffic model and C-DRx configuration |
follow previous RAN1 agreement |
|
Subcarrier spacing |
120 kHz |
UE density/NW Load |
Follow previous RAN1 agreements |
|
Simulation bandwidth |
100 MHz |
Maximum supported Modulation and coding scheme |
Up to 256QAM |
|
Number of carriers |
1 CC |
Guard band ratio on simulation bandwidth |
|
|
Slot size |
14 OFDM symbols |
Channel estimation |
Ideal |
|
BS antenna configuration |
2 TxRU: Baseline: [(M,
N, P, Mg, Ng; Mp, Np) = (4,4,2,1, Optional: (M, N, P, Mg, Ng)=(8:16:2:2:2)] |
HARQ scheme |
Ideal |
|
Total Tx power |
33 dBm, EIRP limited to 63 dBm (as agreed in ref. conf. set 3) |
Max HARQ retransmission |
3 |
|
BS height |
10m |
Target BLER |
10% of first transmission |
|
BS noise figure |
7 dB |
Power control parameters |
Open loop, Alpha=1, P0=-106 dBm |
|
BS antenna element gain |
8 dBi |
Scheduling algorithm |
PF |
|
UE antenna configuration |
2T/4R, (M, N, P, Mg, Ng; Mp, Np) = (1,2,2,1,1;1,2), (dH, dV) = (0.5λ, N/Aλ) |
Cell selection algorithm |
RSRP Slow Fading |
|
UE max transmit power |
23 dBm |
SS blocks per SSB burst |
Up to 64 |
· Other parameters can be optionally reported.
· Company can optionally report the actual total DL transmit power allocation for the baseline and the proposed technique, if different from the agreed reference configuration.
· For TDD frame structure of e.g. DDDSU, the S slot is assumed as S = 10 DL symbols : 2 Guard symbols :2 UL symbols.
· Additionally, for FR1, include the following SLS assumptions as an optional scenario:
o BS antenna configuration: 4T
o BS Total Tx power: derived based on the scaling methodology
o SS blocks per SSB burst: reduced to 1
o Other assumptions are same as those corresponding to Set 2 reference configuration.
o Additional transition energy is calculated taken into account the discussion and agreements for additional transition energy for Set 1/2/3
o Company to report the details
R1-2208382 Potential enhancements for network energy saving FUTUREWEI
R1-2208425 Discussion on network energy saving techniques Huawei, HiSilicon
R1-2208519 Network energy saving techniques Nokia, Nokia Shanghai Bell
R1-2208562 Discussion on network energy saving techniques Spreadtrum Communications
R1-2208655 Discussion on NW energy saving technique vivo
R1-2208777 Discussion on potential network energy saving techniques China Telecom
R1-2208833 Discussion on network energy saving techniques OPPO
R1-2208988 Network Energy Saving techniques in time, frequency, and spatial domain CATT
R1-2209023 Discussion on network energy saving techniques Fujitsu
R1-2209064 Discussion on Network Energy Saving Techniques Intel Corporation
R1-2209127 Network energy saving techniques Lenovo
R1-2209196 Discussion on NW energy saving techniques ZTE, Sanechips
R1-2209296 Discussions on techniques for network energy saving xiaomi
R1-2209349 Discussion on network energy saving techniques CMCC
R1-2209425 Discussion on network energy saving techniques NEC
R1-2209453 Discussion on physical layer techniques for network energy savings LG Electronics
R1-2209501 On network energy savings techniques MediaTek Inc.
R1-2209592 Discussion on network energy saving techniques Apple
R1-2209612 On Network Energy Saving Techniques Fraunhofer IIS, Fraunhofer HHI
R1-2209618 Discussion on network energy saving techniques Rakuten Symphony
R1-2209633 Discussion on potential network energy saving techniques Panasonic
R1-2209655 Potential techniques for network energy saving InterDigital, Inc.
R1-2209743 Network energy saving techniques Samsung
R1-2209859 Network energy savings techniques Ericsson
R1-2209914 Discussion on NW energy saving techniques NTT DOCOMO, INC.
R1-2209997 Network energy saving techniques Qualcomm Incorporated
R1-2210031 Discussion on potential L1 network energy saving techniques for NR ITRI
R1-2210113 Discussion on Network energy saving techniques CEWiT
[110bis-e-R18-NW_ES-02] – Daewon (Intel)
Email discussion on network energy saving techniques by October 19
- Check points: October 14, October 19
R1-2210348 Discussion Summary #1 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
From Oct 12th GTW session, focus on the following for RAN1#110bis-e
· High level description of potential techniques for TR
· Detailed description of potential techniques for company simulations (does not necessarily need to be RAN1 agreement)
· Critical aspects that need substantial work in other WGs
R1-2210349 Discussion Summary #2 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
Presented in Oct 17th GTW session
R1-2210619 Discussion Summary #3 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
Presented in Oct 19th GTW session
R1-2210620 Discussion Summary #4 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
Decision: As per email decision posted on Oct 20th,
Agreement
The following are description of a potential energy saving techniques being discussed in RAN1. The benefits and performance impact of the candidate techniques are subject to further RAN1 evaluations, while RAN1 is discussing the following techniques may have potential impact to other WGs (FFS: RAN4 impact). The impact is not an exhaustive list nor represent definitive list of impacts to WGs and is subject to further changes as RAN1 progress work for the SI.
The description of the technique does not imply the technique will be automatically captured to the TR, but assumed to be the basis for the description in the TR if agreed. Note that this is only to be used as a starting point to finalized the TR in November.
· Note: further merging of techniques (e.g. #A-6 and #A-1) is not precluded.
· Time domain technique description available in:
o Proposal #2-1H of R1-2210620 Section 3
o Proposal #2-2J of R1-2210620 Section 3
o Proposal #2-3H of R1-2210620 Section 3
o Proposal #2-4H of R1-2210620 Section 3
o Proposal #2-6J of R1-2210620 Section 3
· Frequency domain technique description available in:
o Proposal #3-1I of R1-2210620 Section 3
o Proposal #3-2F of R1-2210620 Section 3
o Proposal #3-3F of R1-2210620 Section 3
· Spatial domain technique description available in:
o Proposal #4-1J of R1-2210620 Section 3
o Proposal #4-2G of R1-2210620 Section 3
· Power domain technique description available in:
o Proposal #5-1I of R1-2210620 Section 3
o Proposal #5-2H of R1-2210620 Section 3
o Proposal #5-3H of R1-2210620 Section 3
o Proposal #5-4H of R1-2210620 Section 3
o Proposal #5-5D of R1-2210620 Section 3
Final summary in R1-2210744.
Please refer to RP-221443 for detailed scope of the SI.
[111-R18-NW_ES] – Yi (Huawei)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2212483 TR 38.864 update for study on network energy savings for NR Huawei
Decision: This draft version incorporates the agreements made in R2-2211067 in RAN2 #119bis-e and in R3-226001 in RAN3 #117bis-e, and is endorsed in principle as version 0.4.0.
Including evaluation methodology, base station energy consumption model, KPIs, and evaluation results.
R1-2210858 Evaluation results and other performance aspects for network energy savings Huawei, HiSilicon
R1-2212541 Discussions on NW energy savings performance evaluation vivo (rev of R1-2211018)
R1-2211085 Discussion on NW energy saving performance evaluation Fujitsu
R1-2211097 NW energy savings performance evaluation Nokia, Nokia Shanghai Bell
R1-2211209 Remaining Issues of Evaluation Methodology and Power Model for Network Energy Saving CATT
R1-2211241 Discussion on performance evaluation of network energy savings Spreadtrum Communications
R1-2212563 Discussion on Network energy saving performance evaluations Intel Corporation (rev of R1-2211410)
R1-2211458 Discussion on NW energy savings performance evaluation OPPO
R1-2211691 Discussion on network energy saving performance evaluation CMCC
R1-2211845 Performance evaluation for network energy saving InterDigital, Inc.
R1-2212738 Evaluation results of NW energy saving techniques ZTE, Sanechips (rev of R1-2211903)
R1-2211994 Discussion on NW energy saving performance evaluation NTT DOCOMO, INC.
R1-2212543 NW energy savings performance evaluation Samsung (rev of R1-2212056)
R1-2213000 NW energy savings performance evaluation Qualcomm Incorporated (rev of R1-2212934, rev of R1-2212745, rev of R1-2212653, rev of R1-2212128)
R1-2212154 Evaluations for network energy savings techniques Ericsson
R1-2212259 NW energy savings performance evaluation MediaTek Inc.
R1-2212301 Discussion on performance evaluation for network energy savings LG Electronics
R1-2212702 FL summary#1 for NW Energy Savings Moderator (Huawei)
Presented in Nov 14th session
R1-2212703 FL summary#2 for NW Energy Savings Moderator (Huawei)
From Nov 16th session
Agreement
The following TP is endorsed for Section 6 of TR38.864
=== start of TP ===
Various techniques in time, frequency, spatial and power domains are studied. Companies’ simulation results as well as evaluation assumption details are gathered in [ref.]. In this document, results as well as some notable assumptions and setting are explicitly present in relevant tables. Also, the categorization of techniques in terms of technical domain and results presentation/tabulation are for study/evaluation purpose. This does not preclude to further merge or combine certain techniques.
=== end of TP ===
Agreement
The following TP is endorsed for Section 6.1.1.2 of TR38.864
=== start of TP ===
The following table captures the simulation results for the schemes that use simplified version of SSB, such as only PSS or only PSS and SSS without PBCH, or PSS and SSS with partial PBCH.
Table 6.1.1-x: BS energy savings by simplified SSB
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT/access delay/latency/UE power consumption |
Reference configuration |
Baseline configuration/assumption |
|
CMCC |
SSB and SIB1 repetition period 40ms, for other 20ms occasions, only PSS and SSS are transmitted. |
cat.2 |
Zero |
15.7% |
/ |
Set 1 |
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
|
SSB and SIB1 repetition period 40ms, for other 20ms occasions, only PSS and SSS are transmitted. |
cat.1 |
Zero |
28.3% |
/ |
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
||
|
vivo |
SSB
structure adaptation including light SSB |
Cat1 |
Zero |
0.9% |
0% |
Set 1 |
Baseline scheme: 20ms SSB and SIB1, 20ms RACH listening |
|
SSB
structure adaptation including light SSB |
Cat1 |
Zero |
1.2% |
0% |
Set 1 |
Baseline scheme: 160ms SSB, 20ms UEWUS listening |
|
|
SSB
structure adaptation including light SSB |
Cat1 |
Zero |
2.4% |
0% |
Baseline scheme: 160ms SSB, 80ms UEWUS listening |
||
|
SSB
structure adaptation including light SSB |
Cat1 |
Zero |
4.4% |
0% |
Baseline scheme: 160ms SSB, 160ms UEWUS listening |
||
|
SSB
structure adaptation including light SSB |
Cat2 |
Zero |
0.7% |
0% |
Baseline scheme: 20ms SSB and SIB1, 20ms RACH listening |
||
|
SSB
structure adaptation including light SSB |
Cat2 |
Zero |
0.8% |
0% |
Baseline scheme: 160ms SSB, 20ms UEWUS listening |
||
|
SSB
structure adaptation including light SSB |
Cat2 |
Zero |
0.8% |
0% |
Baseline scheme: 160ms SSB, 80ms UEWUS listening |
||
|
SSB
structure adaptation including light SSB |
Cat2 |
Zero |
0.8% |
0% |
Baseline scheme: 160ms SSB, 160ms UEWUS listening |
||
|
CEWiT |
simplified SSB with repetition period 20ms, only PSS and SSS with partial PBCH are transmitted in simplified SSB |
Cat.1 |
Zero |
2.4% |
|
Set 1 |
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
Based on the simulation results, at empty load, one result shows that BS energy saving gain can be achieved by 15.7%-28.3% with only PSS and SSS transmitted from SSB, and half-reduced SIB1 transmission One company show that the gain from light SSB only ranges from 0.8% to 4.4%, which slightly increases as the listening periodicity of WUS from UE becomes larger. One result shows that simplified SSB with PSS, SSS and partial PBCH, for empty load and Set 1 reference configuration, 2.4% BS energy savings can be achieved.
No impact on UPT was observed due to empty load.
=== end of TP ===
Agreement
The following TP is endorsed for Section 6.1.1.2 of TR38.864
=== start of TP ===
The following table captures the simulation results for the schemes by which transmission occasion of one or more common signals/channels, which is SIB1 and SSB based on the submitted results, can be skipped.
Table 6.1.1-x: BS energy savings by skipping one or more common signals/channels
|
Company |
ES scheme |
Load scenario |
ES gain (%) |
|
BS Category/Reference configuration/Baseline configuration/assumption |
Other evaluation methodology/assumption details/other performance impact |
|
OPPO |
Transmission occasion of SIB1 with 24 RBs for 20 ms periodicity is skipped |
low load(RU-10%) |
2.6% |
Cat 1 Set 1 SIB1 with 24 RBs for 20 ms periodicity, SSB with 20 RBs for 20 ms periodicity
|
SLS UPT/Access delay/Latency: almost similar with the baseline |
|
|
low load(RU-0.2%) |
3.9% |
SLS UPT/Access delay/Latency: almost similar with the baseline |
||||
|
Samsung |
the number of SSB adaptation |
Medium load: 42 % RU |
1.9%, 2.8%, 3.3% |
Cat 1 Set 1 8 SSBs for FR1 and ssb-periodicity = 20 |
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|
|
Light load: 24 % RU |
3.1%, 6.1%, 7.6% |
|||||
|
Low load: 7.5 % RU |
5.5%, 11.0%, 13.8% |
|||||
|
Low load: 2 % RU |
7.2%, 14.3%, 17.9% |
|||||
|
Medium load: 42 % RU |
2.0%, 3.0%, 3.5% |
Cat 2 Set 1 8 SSBs for FR1 and ssb-periodicity = 20 |
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
2.8%, 4.2%, 4.9% |
|||||
|
Low load: 7.5 % RU |
4.4%, 6.6%, 7.7% |
|||||
|
Low load: 2 % RU |
5.3%, 7.9%, 9.2% |
|||||
|
Medium load: 42 % RU |
3.3%, 5.0%, 5.8%, 6.3%, 6.5%, 6.6% |
Cat 1 Set 3 64 SSBs for FR2 and ssb-periodicity = 20
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 |
|||
|
Light load: 24 % RU |
4.3%, 17.6%, 19.5%, 20.5%, 21.0%, 21.3% |
|||||
|
Low load: 7.5 % RU |
7.1%, 13.6%, 16.9%, 18.5%, 19.3%, 19.7% |
|||||
|
Low load: 2 % RU |
8.3%, 15.9%, 19.7%, 21.6%, 22.6%, 23.0% |
|||||
|
Medium load: 42 % RU |
4.0%, 5.9%, 6.9%, 7.4%, 7.7%, 7.8% |
Cat 2 Set 3 64 SSBs for FR2 and ssb-periodicity = 20
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 |
|||
|
Light load: 24 % RU |
5.4%, 8.1%, 9.5%, 10.2%, 10.5%, 10.7% |
|||||
|
Low load: 7.5 % RU |
8.2%, 12.2%, 14.3%, 15.3%, 15.8%, 16.1% |
|||||
|
Low load: 2 % RU |
9.6%, 14.4%, 16.8%, 18.0%, 18.6%, 18.9% |
|||||
|
Medium load: 42 % RU |
1.1%, 2.2%, 2.7% |
Cat 1 Set 1 8 SSBs for FR1 and ssb-periodicity = 40
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
1.6%, 3.2%, 4.0% |
|||||
|
Low load: 7.5 % RU |
3.1%, 6.1%, 7.7% |
|||||
|
Low load: 2 % RU |
4.2%, 8.3%, 10.3% |
|||||
|
Medium load: 42 % RU |
1.0%, 1.6%, 1.8% |
Cat 2 Set 1 8 SSBs for FR1 and ssb-periodicity = 40
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
1.5%, 2.2%, 2.5% |
|||||
|
Low load: 7.5 % RU |
2.3%, 3.5%, 4.0% |
|||||
|
Low load: 2 % RU |
2.8%, 4.2%, 4.9% |
|||||
|
Medium load: 42 % RU |
1.9%, 3.6%, 4.4%, 4.8%, 5.0%, 5.2% |
Cat 1 Set 3 64 SSBs for FR2 and ssb-periodicity = 40
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 |
|||
|
Light load: 24 % RU |
2.6%, 5.0%, 6.1%, 6.7%, 7.0%, 7.2% |
|||||
|
Low load: 7.5 % RU |
4.0%, 7.6%, 9.4%, 10.4%, 10.8%, 11.0% |
|||||
|
Low load: 2 % RU |
4.8%, 9.2%, 11.4%, 12.5%, 13.1%, 13.3% |
|||||
|
Medium load: 42 % RU |
2.1%, 3.1%, 3.6%, 3.9%, 4.0%, 4.1% |
Cat 2 Set 3 64 SSBs for FR2 and ssb-periodicity = 40 |
FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 |
|||
|
Light load: 24 % RU |
2.9%, 4.3%, 5.1%, 5.4%, 5.6%, 5.7% |
|||||
|
Low load: 7.5 % RU |
4.4%, 6.7%, 7.8%, 8.3%, 8.6%, 8.8% |
|||||
|
Low load: 2 % RU |
5.4%, 8.1%, 9.4%, 10.1%, 10.4%, 10.6% |
|||||
|
Medium load: 42 % RU |
0.6%, 1.1%, 1.4% |
Cat 1 Set 1 8 SSBs for FR1 and ssb-periodicity = 80
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
1.0%, 2.3%, 3.0% |
|||||
|
Low load: 7.5 % RU |
2.5%, 5.9%, 7.6% |
|||||
|
Low load: 2 % RU |
4.5%, 10.7%, 13.8% |
|||||
|
Medium load: 42 % RU |
0.5%, 0.8%, 0.9% |
Cat 2 Set 1 8 SSBs for FR1 and ssb-periodicity = 80
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
0.7%, 1.1%, 1.3% |
|||||
|
Low load: 7.5 % RU |
1.2%, 1.8%, 2.1% |
|||||
|
Low load: 2 % RU |
1.4%, 2.1%, 2.5% |
|||||
|
Medium load: 42 % RU |
1.0%, 1.8%, 2.3%, 2.5%, 2.6%, 2.6% |
Cat 1 Set 3 64 SSBs for FR2 and ssb-periodicity = 80
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 |
|||
|
Light load: 24 % RU |
1.3%, 2.6%, 3.2%, 3.5%, 3.7%, 3.7% |
|||||
|
Low load: 7.5 % RU |
2.1%, 4.1%, 5.0%, 5.5%, 5.8%, 5.9% |
|||||
|
Low load: 2 % RU |
2.6%, 5.0%, 6.2%, 6.8%, 7.1%, 7.2% |
|||||
|
Medium load: 42 % RU |
1.1%, 1.6%, 1.8%, 2.0%, 2.0%, 2.1% |
Cat 2 Set 3 64 SSBs for FR2 and ssb-periodicity = 80 |
FTP3 Model. For each load, reduced the number of SSB transmissions: 32, 16, 8, 4, 2, 1 |
|||
|
Light load: 24 % RU |
1.5%, 2.2%, 2.6%, 2.8%, 2.9%, 2.9% |
|||||
|
Low load: 7.5 % RU |
2.3%, 3.5%, 4.1%, 4.4%, 4.5%, 4.6% |
|||||
|
Low load: 2 % RU |
2.9%, 4.3%, 5.0%, 5.4%, 5.5%, 5.6% |
|||||
|
Medium load: 42 % RU |
0.3%, 0.6%, 0.7% |
Cat 1 Set 1 8 SSBs for FR1 and ssb-periodicity = 160
|
FTP3 Model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
0.5%, 1.3%, 1.6% |
|||||
|
Low load: 7.5 % RU |
1.5%, 3.5%, 4.5% |
|||||
|
Low load: 2 % RU |
3.3%, 7.8%, 10.1% |
|||||
|
Medium load: 42 % RU |
0.3%, 0.4%, 0.5% |
Cat 2 Set 1 8 SSBs for FR1 and ssb-periodicity = 160
|
FTP3 model. For each load, reduced the number of SSB transmissions: 4, 2, 1 |
|||
|
Light load: 24 % RU |
0.4%, 0.6%, 0.7% |
|||||
|
Low load: 7.5 % RU |
0.6%, 0.9%, 1.0% |
|||||
|
Low load: 2 % RU |
0.7%, 1.1%, 1.3% |
|||||
|
Medium load: 42 % RU |
0.5%, 0.9%, 1.1%, 1.3%, 1.3%, 1.3% |
Cat 1 Set 3 64 SSBs for FR2 and ssb-periodicity = 160
|
FTP3
model. |
|||
|
Light load: 24 % RU |
0.7%, 1.3%, 1.6%, 1.8%, 1.9%, 1.9% |
|||||
|
Low load: 7.5 % RU |
2.6%, 7.1%, 9.3%, 10.4%, 11.0%, 11.2% |
|||||
|
Low load: 2 % RU |
6.0%, 16.0%, 21.0%, 23.5%, 24.8%, 25.4% |
|||||
|
Medium load: 42 % RU |
0.5%, 0.8%, 0.9%, 1.0%, 1.0%, 1.1% |
Cat 2 Set 3 64 SSBs for FR2 and ssb-periodicity = 160 |
FTP3
model. |
|||
|
Light load: 24 % RU |
0.8%, 1.1%, 1.3%, 1.4%, 1.5%, 1.5% |
|||||
|
Low load: 7.5 % RU |
1.2%, 1.8%, 2.1%, 2.2%, 2.3%, 2.3% |
|||||
|
Low load: 2 % RU |
1.5%, 2.2%, 2.6%, 2.8%, 2.8%, 2.9% |
|||||
Based on the results,
· One company observed that statically skipping certain SIB1 transmission occasions under Set 1 reference configuration for BS Category 1 can achieve energy saving gain by 2.6%~3.9% compared to the baseline of 20 ms SSB&SIB1 repetition periodicity at low load. No impact to UPT was observed. There is no random access procedure modelled in the simulation, therefore the impact on access delay/latency is not shown.
· One company observed that static adaptation of number of SSB can achieve energy saving gain by 0.3%~25.4% at different scenarios with FTP3 model. The gain generally increases when the traffic load becomes lighter while decreases as the SSB periodicity becomes larger. For a same traffic load and SSB periodicity, the gain increases as the number of SSB can be reduced. For FR2 with larger number of SSB for baseline, there is generally larger gain observed than FR1. Due to reduced number of SSB, access delay is increased. Performance of dynamic adaptation of SSB numbers is not provided. There is no random access procedure modelled in the simulation, therefore the impact on access delay/latency is not shown.
=== end of TP ===
Agreement
The following TP is endorsed for Section 6.1.1.2 of TR38.864
=== start of TP ===
The following show the BS energy savings by configuration/adaptation of longer periodicity of common signals and/or uplink random access opportunities.
Table 6.1.1-x: BS energy savings by adapting SSB/SIB1 periodicities
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT/Access delay/latency/UE power consumption, etc. |
Baseline configuration/assumption/Other notable setting |
|
CMCC
|
SSB periodicity 20ms, SIB repetition period 40ms. |
cat.2 |
Zero |
13.7% |
|
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
|
SSB and SIB1 repetition period 40ms. |
17.6% |
|
||||
|
SSB periodicity 20ms, SIB repetition period 40ms. |
cat.1 |
Zero |
25.7% |
|
||
|
SSB and SIB1 repetition period 40ms. |
28.7% |
|
||||
|
vivo |
Period
adaptation of common signals and channels |
Cat1 |
Zero |
78.8% |
UE power consumption: 0% |
Baseline scheme: 20ms SSB and SIB1, 20ms RACH listening |
|
Cat2 |
16.6% |
UE power consumption: 0% |
||||
|
NOKIA/NSB |
SSB/SIB1/RO monitoring period= 160ms |
Cat 2 |
Zero, Low, Light, Medium |
48.4%, 44.3%, 43.7%, 39.9% |
UPT: 0 Mbps, 83 Mbps, 70 Mbps, 55 Mbps |
SSB/SIB1/random-access
occasion (RO) monitoring periodicity @ 20ms |
|
SSB/SIB1/RO monitoring period= 640ms |
Zero, Low, Light, Medium |
53.6%, 49.0%, 48.8%, 46.1% |
UPT: 0 Mbps, 29 Mbps, 27 Mbps, 25 Mbps |
|||
|
SSB/SIB1/RO monitoring period= 1280ms |
Zero, Low, Light, Medium |
83.6%, 51.3%, 51.7%, 50.6% |
UPT: 0 Mbps, 11.2 Mbps, 11 Mbps, 10.5 Mbps |
|||
|
Spreadtrum |
Prolonging
the periodicity of SSB/SIB1/paging: |
Cat 1 |
Zero |
Set 1- Set 3: 23.8%, 19.6%, 16.3% |
|
1)
SSB burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms. |
|
Cat 2 |
Set 1- Set 3: 9.3%, 8.3%, 9.4% |
|
||||
|
Transmission
window of SSB/SIB1/paging: |
Cat 1 |
Set 1- Set 3: 23.8%, 19.6%, 16.3% |
|
1)
The transmission window periodicity is 1280ms, and the transmission window
duration is 160ms. |
||
|
Cat 2 |
Set 1- Set 3: 51.5%, 47.3%, 20.6% |
|
||||
|
Intel |
Increasing the common channel/signal periodicity |
Cat 1 |
Low |
40.1% |
UPT: 819.66 Mbps Avg
EE* (baseline): 5.10 |
Baseline: EE* is defined as cell throughput (in Mbps) / average power consumption (in relative power), and averaged from all BS. |
|
45.0% |
UPT: 819.66 Mbps Avg
EE (baseline): 5.10 |
Baseline:
SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms |
||||
|
Light |
14.6% |
UPT: 611.45Mbps Avg
EE (baseline): 2.66 |
Baseline:
SSB/PRACH: 20 msec periodicity; SIB periodicity 40ms |
|||
|
16.8% |
UPT: 611.45Mbps Avg
EE (baseline): 2.66 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
||||
|
Medium |
6.2% |
UPT: 457.92Mbps Avg
EE (baseline): 1.50 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
|||
|
7.1% |
UPT: 457.92Mbps Avg
EE (baseline): 1.50 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
||||
|
Cat2 |
Low |
8.2% |
UPT: 819.66Mbps Avg
EE (baseline): 35.82 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
||
|
10.9% |
UPT: 819.66Mbps Avg
EE (baseline): 35.82 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
||||
|
Light |
5.1% |
UPT: 611.45Mbps Avg
EE (baseline): 20.75 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
|||
|
5.8% |
UPT: 611.45Mbps Avg
EE (baseline): 20.75 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
||||
|
Medium |
3.0% |
UPT: 457.92Mbps Avg
EE (baseline): 12.44 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms |
|||
|
3.4% |
UPT: 457.92Mbps Avg
EE (baseline): 12.44 |
Baseline:SSB/PRACH:
20 msec periodicity; SIB periodicity 40ms. |
||||
|
CATT |
Adaptation of common signals and channels |
Cat 1
|
Zero load |
10.2%, 72.7%, 84.8% |
|
Baseline: 20ms SSB; ES scheme: SSB: 40ms, 80ms, 160ms for each load |
|
Low load |
3.4%, 18.8%, 19.7% |
|
Baseline: SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms; ES scheme: SSB: 40ms, 80ms, 160ms for each load |
|||
|
Light load |
1.9%, 5.2%, 5.6% |
|
Baseline: SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms; ES scheme: SSB: 40ms, 80ms, 160ms for each load |
|||
|
Medium load |
1.3%, 2.2%, 2.6% |
|
Baseline: SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms; ES scheme: SSB: 40ms, 80ms, 160ms for each load |
|||
|
Fujitsu |
SSB/SIB1 period= 40ms |
Cat2 |
Zero, low, light, medium |
17.9%, 13.7%, 11.1%, 8.6% |
|
Baseline scheme: 20 ms SSB/SIB1 period |
|
SSB/SIB1 period= 80ms |
Zero, low, light, medium |
26.8%, 20.6%, 16.7%, 12.8% |
|
|||
|
SSB/SIB1 period= 160ms |
Zero, low, light, medium |
31.4%, 24.1%, 19.4%, 15.0% |
|
|||
|
SSB/SIB1 period= 40ms |
Zero, low, light, medium |
18.3%, 12.6%, 9.4%, 6.9% |
|
|||
|
SSB/SIB1 period= 80ms |
Zero, low, light, medium |
27.4%, 18.8%, 14.1%, 10.4% |
|
|||
|
SSB/SIB1 period= 160ms |
Zero, low, light, medium |
32.0%, 22.0%, 16.5%, 12.1% |
|
|||
|
Ericsson |
40ms SSB+SIB1 |
Cat1 |
Zero |
0.9% |
|
Baseline scheme: 20ms SSB + 160ms SIB1 ES: one SSB. Energy calculation: per symbol energy consumption is modeled. |
|
80ms SSB+SIB1 |
48.5% |
|
||||
|
160ms SSB+SIB1 |
72.6% |
|
||||
|
40ms SSB+SIB1 |
-6.2% |
|
Baseline scheme: 20ms SSB + 160ms SIB1 ES: Four SSBs. Energy calculation: per symbol energy consumption is modeled. |
|||
|
80ms SSB+SIB1 |
43.8% |
|
||||
|
160ms SSB+SIB1 |
70.5% |
|
||||
|
Qualcomm |
Adaptation of Common Signals and Channels |
Category 1 |
No Load |
13.9% |
Access delay/latency: additiona 20 ms; UE power consumption increment: 99% |
Note: "SSB period of 40 ms" without any network traffic either in DL or UL. Therefore, there are no statistics for UPT, latency, etc.. |
Based on the results with static configurations from 9 sources, it can be observed that longer SSB/SIB1 periodicity can bring BS with significant energy savings in most cases, compared to a selected baseline, for both BS Categories, under all reference configurations. When other configurations/settings are the same, the saving gain generally increase as the periodicity becomes larger, and decrease as the traffic load increases or the number of SSBs increases. Particularly, there are two companies providing results with SSB periodicity larger than 160ms which is the maximum value that is currently supported, i.e., being 640ms and 1280ms, and observed that together with longer SIB1/RACH/RO monitoring periodicities, then depending on the traffic load, the BS energy saving gain can be 53.6%~7.1% and 83.6%~3.4%, respectively, compared to a baseline with 20ms SSB periodicity.
The scheme does not affect the UPT for empty load case. When traffic occurs and load increases, the UPT also significantly decreases. The latency/access delay/UE power consumption increases proportionally as the periodicity of SSB/SIB increases compared to a corresponding baseline.
Performance of dynamic SSB/SIB1 periodicity adaptation is not provided.
=== end of TP ===
Agreement
The following TP is endorsed for Section 6.1.1.2 of TR38.864
=== start of TP ===
The following show the BS energy savings by configuration/adaptation of transmission patterns of common signals, i.e. Paging or SSB based on the submitted results.
Table 6.1.1-x: BS energy savings by adapting Paging/SSB transmission patterns
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT/access delay/latency/UE power consumption |
Reference configuration |
Baseline configuration/assumption |
Other evaluation methodology/assumption details/notable settings |
|
Intel |
Enhanced Paging by increasing the number of consecutive POs within a PF by factor of M while reducing PF density by a factor of M. This keeps the total number of POs same within the DRX cycle. |
Cat1 |
Zero, Paging load 2% |
21.2% |
|
Set 1 |
Paging
Parameters: |
No
C-DRX used for UEs; Paging load is the average load per simulation run time. Paging events were randomly generated. Same as below results. The value of T is larger than 160ms. |
|
Zero, Paging load 0.2% |
4.0% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Zero, Paging load 2% |
42.3% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Zero, Paging load 0.2% |
6.7% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Zero, Paging load 3.6% |
18.9% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Zero, Paging load 0.5% |
0.2% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Zero, Paging load 3.6% |
26.4% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Zero, Paging load 0.5% |
0.3% |
|
Paging
Parameters: |
No
C-DRX used for UEs; |
||||
|
Qualcomm |
Adaptation of Common Signals and Channels |
Category 1 |
No Load |
10.3% |
UE power consumption: -4% |
FR2 Set 3 |
|
"Compact SSB" without any network traffic either in DL or UL. Therefore, there are no statistics for UPT, latency, etc.. |
Based on the results,
· One company observed that for BS category 1 and at empty load case, statically adapting paging configuration could provide BS energy savings by 0.3%~6.7% when paging load (resource used for paging) is 0.2%~0.5%, and the gain can be up to 42.3% when paging load is increased up to 3.6%. The gain could also increases as the number of SSB increases. Performance of dynamically adapting paging configurations is not provided. The above energy saving gains were achieved with SSB periodicity of 80ms or 160ms.
· One company observed that having compact SSB (i.e., no time gap between consecutive SSBs) could provide 10.3% network energy saving for BS category 1 and at empty load case in FR2 when SSB periodicity is 20ms. Furthermore, UE power saving can be improved by 4%.
=== end of TP ===
Agreement
The following TP is endorsed for Section 6.1.1.2 of TR38.864
=== start of TP ===
The following show the BS energy savings by dynamically adapting common signals, i.e. RACH based on the submitted results.
Table 6.1.1-x: BS energy savings by dynamically adapting RACH periodicity/occasions
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT/access delay/latency/UE power consumption |
Reference configuration |
Baseline configuration/assumption/notable settings |
Other evaluation methodology/assumption details |
|
Ericsson |
PRACH periodicity= 20ms |
Cat1
|
Zero |
14.4% |
Access delay/latency: 10ms increase |
Set 1 |
Baseline scheme: 20 ms SSB, 40ms SIB1 period, 10ms PRACH periodicity. Per symbol energy consumption is modeled. ES scheme: adapting PRACH periodicity for energy efficiency via dynamic PRACH occasions adaptation. Note separate evaluation performed for different PRACH periodicities (i.e. no switching between these settings). |
1 SSB
|
|
PRACH periodicity= 40ms |
20.9% |
Access delay/latency: 30ms increase |
||||||
|
PRACH periodicity= 80ms |
22.2% |
Access delay/latency: 70ms increase |
||||||
|
PRACH periodicity= 20ms |
17.3% |
Access delay/latency: 10ms increase |
four SSBs
|
|||||
|
PRACH periodicity= 40ms |
23.9% |
Access delay/latency: 30ms increase |
||||||
|
PRACH periodicity= 80ms |
24.9% |
Access delay/latency: 70ms increase |
Based
on the results with multiple static RACH occasion configurations, it
is one company observed that adaptation of RACH occasions can achieve BS
energy savings by 14.4%~24.9% for BS Category 1 at empty load case under FR1
TDD compared to 10ms RACH periodicity without adaptation. The gain generally
increases as PRACH periodicity increases for the same number of SSBs.
Performance of dynamic RACH configuration is not provided.
On UPT/access delay/latency, this scheme increases access delay/latency from 10ms to 70ms, proportional to the increased PRACH periodicity.
=== end of TP ===
R1-2212935 FL summary#3 for NW Energy Savings Moderator (Huawei)
From Nov 18th session
Agreement
The following TP is endorsed for Section 6.1.1.2 of TR38.864
=== start of TP ===
The following show the BS energy savings by scheduling of SIB1 by SSB, without PDCCH for SIB1, with repetition period 20ms.
Table 6.1.1-x: BS energy savings by scheduling of SIB1 by SSB
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT Access delay/latency UE power consumption Other KPI(s), if any |
Reference configuration |
Baseline configuration/assumption |
Traffic model |
Other evaluation methodology/assumption details - Part 1 (other than power modeling aspects) |
Other evaluation methodology/assumption details - Part 2 (power modeling aspects) |
|
CEWiT+B417:R417 |
Scheduling of SIB1 by SSB, without PDCCH for SIB1, with repetition period 20ms |
Cat.1 |
Zero |
4.8% |
|
Set 1 |
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
|
numerical analysis |
•SIB1:
PDCCH: 3 symbols; PDSCH: 12 OFDM symbols including DMRS. |
|
CEWiT [R1-2212429, |
Scheduling of SIB1 by SSB, without PDCCH for SIB1, 4 beams, with repetition period 20ms |
Cat.1 |
Zero |
11.4% |
|
Set 1 |
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
|
numerical analysis |
•SIB1: PDCCH: 3 symbols; PDSCH: 12 OFDM symbols including DMRS. •ղ=1,
A=0.4. |
|
CEWiT |
Scheduling of SIB1 by SSB, without PDCCH for SIB1, 8 beams, with repetition period 20ms |
Cat.1 |
Zero |
14.8% |
|
Set 1 |
Baseline: normal SSB/SIB1 transmission, with 20ms repetition period for both. |
|
numerical analysis |
•SIB1: PDCCH: 3 symbols; PDSCH: 12 OFDM symbols including DMRS. •ղ=1,
A=0.4. |
It is observed on one source that using SSB to schedule SIB1 can obtain 4.8%~14.8% BS energy savings for Set 1 reference configuration for BS Category 1, compared to SSB/SIB1 periodicity of 20 ms for both.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for waking up gNB triggered by UE wake up signal (WUS).
Table 6.1.1-x: BS energy savings by UE wake up signal (WUS)
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT |
Access delay/latency |
UE power consumption |
Reference configuration |
Baseline configuration/assumption |
Traffic model |
Other evaluation methodology/assumption details/notable settings |
|
MTK |
UE_can_wake_up_gNB |
Cat 1 |
Low |
49.3% |
0.00% |
0.00% |
0.07% |
Set 1 |
All 21 cells active |
VoIP |
SLS;
DRX (40, 4, 10); 9 out of 21 cells remian active. |
|
Cat 2 |
51.9% |
0.00% |
0.00% |
0.07% |
|||||||
|
ZTE,
Sanechips |
UE WUS is used to wake up a gNB in an energy saving state without DL transmission including SSB/SIB1 |
1 |
low |
7.4% 19.6% 23.8% |
0.66% 2.59% 5.04% |
|
|
Set 1 |
no WUS, cell is in a normal state with {20ms/40ms} SSB/SIB periodicity |
FTP3 |
UE
mobility. WUS period=20ms/80ms/160ms for each load. |
|
light |
4.9% 12.7% 15.5% |
0.11% 0.43% 0.86% |
|
|
|||||||
|
2 |
low |
6.2% 6.4% 6.5% |
0.66% 2.59% 5.04% |
|
|
no WUS, cell is in a normal state with {20ms/40ms} SSB/SIB periodicity |
|||||
|
light |
4.5% 4.6% 4.7% |
0.11% 0.43% 0.86% |
|
|
|||||||
|
vivo |
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
Cat 1 |
0% |
29.7% 66.6% 80.7% |
|
|
0.00% 0.00% 0.00% |
Set 1 |
legacy
BS, where all cells are always in the normal mode. |
NaN NaN NaN |
SLS |
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
0.002% |
27.3% 60.4% 72.8% |
0.8% 15.5% 21.7% |
5.68% 38.73% 39.53% |
0.00% 0.00% 0.00% |
FTP3, mean packet interval of 10s, packet size of 100bytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
20.55% 20.81% 20.49% |
0.8% 4.3% 6.0% |
3.4% 4.5% 8.6% |
9.70% 20.72% 32.51% |
0.98% 1.46% 1.66% |
FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
41.79% 41.17% 41.35% |
-2.4% 0.3% 0.1% |
2.7% 6.0% 7.2% |
8.95% 14.55% 20.53% |
1.13% 1.51% 1.97% |
||||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
0% |
32.1% 69.6% 83.7% |
|
|
0.00% 0.00% 0.00% |
NaN NaN NaN |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
0.002% |
29.4% 63.3% 75.6% |
0.8% 16.5% 24.2% |
4.17% 38.05% 39.53% |
0.00% 0.00% 0.00% |
FTP3, mean packet interval of 10s, packet size of 100bytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
20.71% 20.51% 20.66% |
-0.1% 6.4% 6.6% |
3.9% 7.0% 8.7% |
11.04% 20.31% 29.07% |
1.08% 1.33% 1.65% |
FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
41.74% 41.91% 42.07% |
-2.2% -0.7% -0.6% |
1.3% 6.6% 7.5% |
10.32% 16.58% 18.21% |
1.13% 1.63% 1.84% |
||||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
Cat 2 |
0% |
19.1% 19.4% 19.4% |
|
|
0.00% 0.00% 0.00% |
NaN NaN NaN |
||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
0.002% |
18.1% 18.3% 18.3% |
0.76% 5.40% 11.79% |
0.58% 8.98% 20.16% |
0.00% 0.00% 0.00% |
FTP3, mean packet interval of 10s, packet size of 100bytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
20.58% 20.28% 20.76% |
0.5% 1.0% -0.4% |
0.69% 1.02% 2.88% |
7.93% 9.93% 17.27% |
0.64% 0.56% 0.99% |
FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
41.46% 41.22% 41.04% |
-2.4% -2.1% -1.8% |
0.05% 0.30% 0.45% |
5.94% 10.07% 11.62% |
0.99% 1.10% 0.96% |
||||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
0% |
20.3% 20.6% 20.6% |
|
|
0.00% 0.00% 0.00% |
NaN NaN NaN |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
0.002% |
19.2% 19.4% 19.5% |
0.85% 4.17% 10.53% |
2.63% 9.83% 20.86% |
0.00% 0.00% 0.00% |
FTP3, mean packet interval of 10s, packet size of 100bytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
20.55% 20.61% 21.26% |
0.5% 0.3% -1.0% |
0.36% 0.61% 2.21% |
8.30% 10.14% 17.32% |
0.71% 0.73% 1.11% |
FTP3, mean packet interval of 200ms, packet size of 0.5Mbytes |
|||||
|
UE
WUS to wake up a ES gNB without or with sparse SSB/SIB1 and RACH monitoring |
42.05% 41.38% 41.74% |
-3.1% -2.3% -2.9% |
0.10% 0.21% 0.36% |
7.48% 9.16% 10.22% |
1.26% 0.98% 1.04% |
||||||
|
NOKIA/NSB |
Wake up of gNB triggered by UE wake up signal (WUS) @ 20ms |
Cat 2 |
Low |
45.6% |
13,01 Mbps |
|
|
Set 1 |
SSBs/SIB1s/RO
monitoring @ 20ms default periodicity |
UL - IM |
SLS+Post-processing |
|
Wake up of gNB triggered by UE wake up signal (WUS) @ 160ms |
51.9% |
6,08 Mbps |
|
|
|||||||
|
Wake up of gNB triggered by UE wake up signal (WUS) @ 640ms |
52.5% |
2,15 Mbps |
|
|
|||||||
|
Wake up of gNB triggered by UE wake up signal (WUS) @ 1280ms |
66.7% |
1,16 Mbps |
|
|
|||||||
|
Samsung |
Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicy |
Cat 1 |
Low |
70.3% 64.0% 57.2% |
|
0.00% 0.00% 0.00% |
|
Set 2 |
SR periodicity = 10ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
SLS |
|
Wake up of gNB triggered by UE wake up signal (WUS), @15 ms WUS periodicy |
76.4% 69.4% 61.8% |
|
0.00% 0.00% 0.00% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicy |
80.1% 73.7% 66.7% |
|
0.00% 0.00% 0.00% |
|
SR periodicity = 10ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
SLS |
||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @15 ms WUS periodicy |
83.7% 76.5% 68.8% |
|
0.00% 0.00% 0.00% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicy |
92.8% 86.2% 79.0% |
|
0.00% 0.00% 0.00% |
|
SR periodicity = 10ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
SLS |
||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @15 ms WUS periodicy |
93.0% 85.7% 77.8% |
|
0.00% 0.00% 0.00% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicy |
45.0% 39.2% 32.8% |
|
-29.56% -28.9% -29.41% |
|
SR periodicity = 10ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
SLS |
||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicy |
39.1% 32.6% 25.7% |
|
-45.37% -45.15% -45.51% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicy |
67.1% 60.2% 52.7% |
|
-22.44% -22.85% -22.79% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicy |
64.7% 58.5% 51.8% |
|
-29.56% -28.9% -29.41% |
|
SR periodicity = 10ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
SLS |
||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicy |
60.8% 54.1% 46.7% |
|
-45.37% -45.15% -45.51% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicy |
78.0% 70.9% 63.2% |
|
-22.44% -22.85% -22.79% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicy |
90.0% 83.4% 76.3% |
|
-29.56% -28.9% -29.41% |
|
SR periodicity = 10ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
SLS |
||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @5 ms WUS periodicy |
88.9% 81.6% 73.8% |
|
-45.37% -45.15% -45.51% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Wake up of gNB triggered by UE wake up signal (WUS), @10 ms WUS periodicy |
92.0% 84.7% 76.8% |
|
-22.44% -22.85% -22.79% |
|
SR periodicity = 15ms |
FTP3, mean packet interval of 2s, UL traffic only, 1/5/10 UE |
|||||
|
Qualcomm |
Wake up of gNB triggered by UE two symbol wake up signal (WUS) |
Category 1 |
No Load |
18.7% |
|
FR2 Set 3 |
"light SSB" combined with UL WUS and on demand SIB 1 |
||||
For UE WUS signal triggering SSB/SIB1/RACH for RRC IDLE/INACTIVE/CONNECTED mode, based on results from 4 sources, it is observed that, with UE WUS signal triggering a BS of 100% detection assumption,
· With C-DRX, at low load, one source observed about 50% network energy savings with marginal UE power increment, without UPT loss observed. The scheduling delay when switching to a new gNB is not modelled.
· For the evaluations with assumption of RRC_IDLE/INACTIVE mode without C-DRX,
o without DL transmission including DL common signals before gNB reception of WUS, with WUS period of 20ms, 80ms and 160ms, at zero or low load, the network energy savings could be 7.4%~32.1% (6.2%~45.6%), 19.6%~69.6% (6.4%~51.9%), 23.8%~ 83.7% (6.5%~52.5%) respectively by using Category 1 (Category 2) BS power model. The savings can increase as the WUS period increases, and decrease as the traffic load increases. When WUS period is 20ms, marginal UPT loss, access delay/latency increment and UE power consumption increment are observed. The UPT loss and access delay/latency increases as WUS periodicity increases, while there is marginal UE power consumption increment.
o With sparse SSB of 160ms periodicity transmitted before gNB reception of WUS, at zero or low load, 27.3%~29.7% (18.1%~19.1%), 60.4%~66.6% (18.3%~19.4%), 72.8%~80.7% (18.3%~19.4%) network energy savings can be achieved with WUS period of 20ms, 80ms and 160ms respectively by using Category 1 (Category 2) BS power model. When WUS period is 20ms, marginal UPT loss, access delay/latency increment and UE power consumption increment are observed. The UPT loss and access delay/latency increases as WUS periodicity increases, while there is marginal UE power consumption increment.
· Note: gNB coordination for WUS reception is assumed. Resource configuration for WUS is not specifically modelled, while one source assumes the configuration of WUS can be obtained from a camping cell. For the case of no DL transmission, also gNB synchronization is further assumed.
· Note: For evaluation results from 2 source, it is assumed that UE achieves timing for the UL WUS transmission from the other cell. For evaluation results from 2 source, it is assumed that UE achieves synchronization with the gNB targeted for energy saving utilizing discovery signal from the same cell, and one source assumed the discovery signal contains PSS only and its use is to help the UE to get synchronized and to be able to transmit an uplink trigger signal. The differentiation of multiple gNBs which has detected the WUS is not modelled.
o The detection of WUS is assumed to be ideal. False triggering for detection of targeting gNB is not considered.
For UE WUS signal triggering gNB to wake up in case of uplink traffic arrival, for RRC_CONNECTED without C-DRX and without DL common signals/DL transmission other than PDCCH carrying UL grant, with the assumption of a separate receiver used and 100% detection assumption, at low load, 1 source observed that,
· With WUS detection power of 10, 55 or, with 90 which has the same active UL power
o When the WUS periodicity is same as the baseline of SR periodicity, 77.8%~93%, 66.7%~92.8% or 57.2%~76.4% network energy savings could be achieved respectively;
o When the WUS periodicity is smaller than the SR periodicity of the baseline, 76.3%~92%, 46.7%~78% or 25.7%~67.1% network energy savings could be achieved respectively;
o For each case, the gain generally increases as the WUS periodicity increases and decreases as the traffic load increases. The gain could also increase as the gNB detection power decreases.
o There is latency reduction observed, which could increase as the periodicity of WUS decreases. The gain can be up to 45%.
· The assumption is that gNB needs to wake up to detect SR but can detect WUS during sleep state. gNB is assumed to be in a state such that the main UL receiver is still in deep sleep when detecting wake-up signal and gNB is able to wake up from deep sleep to active in one slot after WUS detection. The WUS receiver is assumed to be active only when detection of WUS signal and becomes 0 power in other time.
When combined with a light version of SSB and on demand SIB1, one source observed 18.7% network energy savings at low load for FR2, assuming the light version of SSB contains PSS only and its use is to help the UE to get synchronized and to be able to transmit an uplink trigger signal.
=== end of TP ===
Agreement
=== start of TP ===
The following captures the results for adaptation of UE DTX/DRX.
Table 6.1.1-x: BS energy savings by adaptation of UE DTX/DRX
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT |
Access delay/latency/UE power consumption/Other KPI(s), if any |
a) Reference configuration b) Baseline configuration/assumption c) Traffic model d) Other evaluation methodology/assumption details/notable settings |
|||
|
MTK |
DRX_offset_alignment |
Cat 1 |
Low |
29.8% |
0.91% |
Access delay/latency: 0.92% UE power consumption: 2.17% |
Set 1 Random DRX offset (granularity = 5 ms) VoIP SLS; DRX (40, 4, 10); DRX offset aligned to 0 |
|||
|
Cat 2 |
13.7% |
0.91% |
||||||||
|
OPPO |
DRX align |
Cat 1 |
low load(RU-9.3%) |
4.7% |
361.08Mbps(-15.5%) |
Access delay/latency: 78.03ms(+50%) |
Set 1 UE-specific DRX, SSB with 20 RBs for 20 ms periodicity |
FTP (0.5MB as packet size, 200ms as mean inter-arrival time) |
SLS, C-DRX config: FTP (160,100,8), DRX align |
|
|
low load(RU-0.15%) |
6.7% |
85.91Mbps(-8.7%) |
Access delay/latency: 143.55ms(+3.83%) |
IM (0.1MB as packet size, 2s as mean inter-arrival time) |
SLS, C-DRX config: IM (320,80,10), DRX align |
|||||
|
DRX align and dropping SSB outside UE active time |
low load(RU-9.3%) |
14.4% |
361.08Mbps(-15.5%) |
Access delay/latency: 78.03ms(+50%) |
FTP (0.5MB as packet size, 200ms as mean inter-arrival time) |
SLS, C-DRX config: FTP (160,100,8), DRX align and dropping SSB outside UE active time |
||||
|
low load(RU-0.15%) |
70.1% |
85.91Mbps(-8.7%) |
Access delay/latency: 143.55ms(+3.83%) |
IM (0.1MB as packet size, 2s as mean inter-arrival time) |
SLS, C-DRX config: IM (320,80,10), DRX align and dropping SSB outside UE active time |
|||||
|
ZTE,
Sanechips |
DRX alignment |
1 |
low |
0.3% 0.9% |
5% 1.30% |
unfinished packet ratio=(total number of unfinished packet for baseline-total number of unfinished packet for enhanced)/total number of unfinished packet for baseline: 50%, 54.5% for each BS caterogy |
Set 1 UE-specific CDRX FTP3 CDRX pattern for FTP3 CDRX alignment in a cell |
|||
|
2 |
0.2% 0.4% |
5% 1.30% |
||||||||
|
Spreadtrum |
traffic concentration (in a transmission window |
Cat 1 |
Low |
37.8% 34.9% 30.9% |
|
|
a) For each BS Category: Set 1, Set 2, Set 3 b)- 1) There are 5% load (UE specific data) in 40 slots every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) Scaling: Sf≈0.21 in 2 slots every 20ms, and Sf≈0.05 in 38 slots every 20ms c)-1) The load is concentrated in first 10ms. There are 10% load (UE specific data) in the first 20 slots every 20ms, zero load in the last 20 slots every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) gNB can enter light sleep for Cat 1, but can only enter micro sleep for Cat 2. 3) Scaling: Sf≈0.26 in 2 slots every 20ms, and Sf≈0.1 in 18 slots every 20ms d)- 1) 160ms duration in total. 2) SSB
burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms. Two SSBs
and the corresponding SIB1 share a slot. SSB burst and SIB1 take 40 PRBs. 3)
PF periodicity at gNB side is 20ms (T=1280ms, N=64). Paging is transmitted in
another slot every PF assuming one PO is effective in each PF. Paging takes
40 PRBs. 4) Scaling: Sa=1, Sp=1, P_static=P3. |
|||
|
Cat 2 |
31.1% 27.7% 29.2% |
|
|
|||||||
|
Offload between cells (the offloaded cell is turned off) |
Cat 1 |
Low |
57.7% 53.5% 47.9% |
|
|
a) For each BS Category: Set 1, Set 2, Set 3 b)-1) Cell #1 and cell #2: There are 5% load (UE specific data) in 40 slots every 20ms. The load is frequency multiplexed with SSB burst and SIB1 in 2 slots every 20ms. 2) Scaling: Sf≈0.21 in 2 slots every 20ms, and Sf≈0.05 in 38 slots every 20ms c)-1) The load in cell #1 is shifted to
cell #2. d)-1) 160ms duration in total. 2) SSB
burst periodicity is 20ms, and SIB1 repetition periodicity is 20ms. Two SSBs
and the corresponding SIB1 share a slot. SSB burst and SIB1 take 40 PRBs. 3)
PF periodicity at gNB side is 20ms (T=1280ms, N=64). Paging is transmitted in
another slot every PF assuming one PO is effective in each PF. Paging takes
40 PRBs. |
||||
|
Cat 2 |
46.5% 44.3% 46.6% |
|
|
|||||||
|
Intel |
Enhanced C-DRX |
Cat1 |
Light |
2.8% |
Baseline:
122.3 Mbps |
Avg
EE (baseline): 5.20 |
a)Set1 c) FTP3 d)
SLS |
Baseline
DRX Parameters: |
||
|
Medium |
29.7% |
Baseline:
93.2 Mbps |
Avg
EE (baseline): 1.87 |
|||||||
|
Low |
2.3% |
Baseline:
111.2 Mbps |
Avg
EE (baseline): 8.81 |
Baseline
DRX Parameters: |
||||||
|
Light |
2.3% |
Baseline:
98.1 Mbps |
Avg
EE (baseline): 5.31 |
Baseline
DRX Parameters: |
||||||
|
Light |
2.6% |
Baseline:
98.1 Mbps |
Avg
EE (baseline): 5.31 |
Baseline
DRX Parameters: |
||||||
|
Medium |
30.9% |
Baseline:
75.0 Mbps |
Avg
EE (baseline):1.97 |
Baseline
DRX Parameters: |
||||||
|
Medium |
4.8% |
Baseline:
75.0 Mbps |
Avg
EE (baseline):1.97 |
Baseline
DRX Parameters: |
||||||
|
CATT |
Adaptation of DTX/DRX |
Cat 1 |
Low load |
71.4% |
|
|
Set1 |
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms; |
FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes |
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);DTX configuration: gNB starting offset of DTX on locate before UE DRX on duration in order to support UE wakeup;SSB periodicity: 20ms; CSI-RS/TRS periodicity: 10ms. |
|
Light load |
62.6% |
|
|
FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes |
||||||
|
Medium load |
47.8% |
|
|
FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes |
||||||
Based on 6 sources results, semi-static UE C-DRX alignment achieves BS energy savings gain by 0.2%~71.4% depending on the traffic, UE DRX configurations, and the assumed baseline e.g. random DRX offset per UE, or gNB is always ON to provide service to the UE. At low or light traffic load cases, 4 sources show that the gain can be 14.4%~71.4%, while 3 sources show less than 6.7% gain, depending on whether BS and UE active duration are aligned or not; at medium load case, 2 sources show network energy saving gain can be 4.8%~47.8%. According to one source, dropping SSB outside UE active time can achieve the energy savings by 14.4%~70.1% and it is assumed that the UE active durations are aligned and the potential impact on synchronization and UE measurement outside the UE duration is not considered.
On UPT, one result shows there is marginal negative impact while one result shows it can be up to 15.5%. Also, one result shows that the impact on UPT varies: when the UE DRX cycle is 160ms and gNB active time is 80ms, the UPT is increased while in other configurations, there can be large UPT loss.
On access delay/latency, one result shows marginal increment while one result shows the increment can be up to 50%. Also, about 50% unfinished packet ratio is observed from one source compared to the baseline without UE C-DRX alignment during the evaluation period. The increments are related to the DRX configuration.
Additionally, one source shows that at low and medium load, the average EE is increased up to 28.93% when UE DRX alignment is assumed, whereas for light load case, average EE decreases up to 12.24% when UE DRX alignment is assumed.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for adaptation of SSB and/or SIB1.
Table 6.1.1-x: BS energy savings by adaptation of SSB and/or SIB1
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT |
Access delay/latency/UE power consumption/Other KPI(s), if any |
Reference configuration |
Baseline configuration/assumption |
Traffic model/Other evaluation methodology/assumption details/notable settings |
|
CATT |
Adaptation of SSB/SIB1 |
Cat 1 |
Low load |
22.0% |
|
|
set1 |
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms; |
FTP3,
inter-arrival time = 200ms, packet size = 0.5Mbytes. |
|
43.4% |
|
|
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms;DTX configuration: gNB starting offset of DTX on locate before UE DRX on duration in order to support UE wakeup; |
||||||
|
Ericsson |
20ms Discovery signal (4 symbols) + no SIB1 |
Cat1 |
Zero |
2.6% / 5.9% |
|
|
Set 1 |
Baseline scheme: 20ms SSB + 160ms SIB1 |
one
SSB/ four SSBs |
|
Qualcomm |
on-demand SIB1 |
Cat 1 |
Empty load |
5.8% / 7.7% / 8.6% |
|
|
Set 1 |
Baseline: 20ms periodicity for
SSB/SIB1/RO, one beam |
|
|
32.1% / 36.6% / 38.8% |
|
|
Baseline: 20ms periodicity for
SSB/SIB1/RO, 8 beams |
|
One source shows that with a 4-symbol Discover signal (DRS), and without SIB1 transmission and for on-demand SIB1, 2.6% and 5.9% energy savings can be achieved for one SSB and four SSB respectively, at empty load with baseline of 20ms SSB/160ms SIB1 periodicity.
One source shows on-demand SSB can achieve BS energy savings by 22.0%/43.4% at low load compared to a baseline of 20ms SSB/SIB1 periodicity with or without gNB DTX configuration.
One source is provided with on-demand SIB1 at empty load with baseline of 20ms SSB/SIB1 periodicity, 5.8%~8.6% BS energy savings can be achieved at SIB1 transmission rate of 20%~5% for one SSB beam, and the gains can increase to 32.1%~38.8% for 8 beams case for a same SIB1 transmission rate range.
Performance impact of on demand SSB/SIB was not provided.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results by multi-carrier energy savings enhancements.
Table 6.1.1-x: BS energy savings by multi-carrier enhancements
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
KPI |
Baseline configuration/assumption |
|
Huawei，HiSilicon |
Inter-band SSB-less on Scell |
Cat 2 |
0% load(zero) |
14.4% |
|
4 SSB beams with 20ms period, 20RB
2 SSB per slot, and 4 symbols for each SSB, when the SSB is transmitted on a carrier |
|
10% load(low) |
9.3% |
|||||
|
20% load(light) |
7.4% |
|||||
|
30% load(medium) |
5.7% |
|||||
|
ZTE, Sanechips |
SSB-less SCell |
1 |
zero load |
97.4% |
|
SSB20ms for baseline; set 1; |
|
93.9% |
SSB80ms for baseline; set 1; |
|||||
|
88.4% |
SSB160ms for baseline; set 1; |
|||||
|
2 |
83.8% |
SSB20ms for baseline; set 1; |
||||
|
82.4% |
SSB80ms for baseline; set 1; |
|||||
|
82.1% |
SSB160ms for baseline; set 1; |
|||||
|
1 |
97.3% |
SSB20ms for baseline; set 2; |
||||
|
93.8% |
SSB80ms for baseline; set 2; |
|||||
|
88.3% |
SSB160ms for baseline; set 2; |
|||||
|
2 |
82.1% |
SSB20ms for baseline; set 2; |
||||
|
80.7% |
SSB80ms for baseline; set 2; |
|||||
|
80.4% |
SSB160ms for baseline; set 2; |
|||||
|
SSB-less SCell with DL traffic |
1 |
low |
58.4% |
UPT:801.79, SSB-less UPT：812.57 UPT gain: 1.3%; SCell activation delay reduced by 6ms |
SSB20ms for baseline; set 1; with DL traffic; SCell activation delay =12 ms |
|
|
35.2% |
UPT:804.41, SSB-less UPT：812.57 UPT gain: 1.0%; Scell activation delay reduced by 6ms |
SSB80ms for baseline; set 1; with DL traffic; Scell activation delay =12 ms |
||||
|
21.2% |
UPT:804.54, SSB-less UPT：812.57 UPT gain: 1.0% Scell activation delay reduced by 6ms |
SSB160ms for baseline; set 1; with DL traffic; Scell activation delay =12 ms |
||||
|
2 |
15.2% |
UPT:801.79, SSB-less UPT：812.57 UPT gain: 1.3%; Scell activation delay reduced by 6ms |
SSB20ms for baseline; set 1; with DL traffic; Scell activation delay =12 ms |
|||
|
7.4% |
UPT:804.41, SSB-less UPT：812.57 UPT gain: 1.0%; Scell activation delay reduced by 6ms |
SSB80ms for baseline; set 1; with DL traffic; Scell activation delay =12 ms |
||||
|
6.1% |
UPT:804.54, SSB-less UPT：812.57 UPT gain: 1.0%; Scell activation delay reduced by 6ms |
SSB160ms for baseline; set 1; with DL traffic; Scell activation delay =12 ms |
||||
|
1 |
72.7% |
UPT:115.80, SSB-less UPT：119.41 UPT gain: 3.1%; Scell activation delay reduced by 6ms |
SSB20ms for baseline; set 2; with DL traffic; Scell activation delay =12 ms |
|||
|
51.7% |
UPT:118.20, SSB-less UPT：119.41 UPT gain: 1.0%; Scell activation delay reduced by 6ms |
SSB80ms for baseline; set 2; with DL traffic; Scell activation delay =12 ms |
||||
|
34.9% |
UPT:118.70, SSB-less UPT：119.41 UPT gain: 0.6%; Scell activation delay reduced by 6ms |
SSB160ms for baseline; set 2; with DL traffic; Scell activation delay =12 ms |
||||
|
2 |
24.9% |
UPT:115.80, SSB-less UPT：119.41 UPT gain: 3.1%; Scell activation delay reduced by 6ms |
SSB20ms for baseline; set 2; with DL traffic; Scell activation delay =12 ms |
|||
|
16.9% |
UPT:118.20, SSB-less UPT：119.41 UPT gain: 1.0%; Scell activation delay reduced by 6ms |
SSB80ms for baseline; set 2; with DL traffic; Scell activation delay =12 ms |
||||
|
15.5% |
UPT:118.70, SSB-less UPT：119.41 UPT gain: 0.6% Scell activation delay reduced by 6ms |
SSB160ms for baseline; set 2; with DL traffic; Scell activation delay =12 ms |
||||
|
SSB-less Scell with UL traffic |
2 |
low |
39.4% |
Scell activation delay reduced by 6ms
|
SSB20ms for baseline; set1; with UL traffic; Scell activation delay =12 ms |
|
|
22.4% |
SSB80ms for baseline; set1; with UL traffic; Scell activation delay =12 ms |
|||||
|
18.7% |
SSB160ms for baseline; set1; with UL traffic; Scell activation delay =12 ms |
|||||
|
Vivo |
Inter-band
CA with SSB-less carriers/Scell |
Cat 1 |
0% |
14.7% |
UE power consumption: 0% |
Baseline scheme: |
|
Cat 2 |
0% |
5.1% |
||||
|
Intel |
inter-band SSB-less Scell |
Cat1 |
Low |
3.0% |
UPT:
1639.3 Mbps;Avg EE (baseline): 6.56; |
Baseline: CC# 2
(Scell): 160 msec SSB, no SIB1/PRACH, |
|
Cat1 |
Light |
1.0% |
UPT:1222.9
Mbps;Avg EE (baseline): 2.96; |
|||
|
Cat1 |
Medium |
0.3% |
UPT:
915.8Mbps;Avg EE (baseline): 1.57; |
|||
|
MTK |
Scell_w/o_SIB1 |
Cat 1 |
Light |
2.3% |
UPT: 0.00%; Access delay/latency: 0%; UE power consumption: 0% |
Scell has SSB and SIB1 |
|
Cat 2 |
1.1% |
|||||
|
Scell_w/o_SSB_SIB1 |
Cat 1 |
7.9% |
||||
|
Cat 2 |
1.3% |
|||||
|
CMCC |
Scell with simplified SSB: Scell with only PSS/SSS, with 20ms periodicity. Pcell with normal SSB, SIB1 and also SIB information for Scell. |
Cat.2 |
Zero |
5.7% |
N/A |
Baseline: normal SSB on Scell. Pcell with normal SSB, SIB1 and also SIB1 information for Scell.
|
|
Cat.1 |
10.5% |
|
||||
|
Vivo |
SSB/SIB-less
carrier operation with assistance of anchor carrier |
Cat 1 |
0% |
14.8% |
|
Baseline scheme: |
|
Cat 2 |
0% |
9.1% |
|
|||
|
CATT |
Multi-carrier energy savings enhancements |
Cat 1 |
Low load |
25.7% |
|
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms;CSI-RS/TRS 10ms;Rel-17 Scell activation/deactivation; |
|
Light load |
24.1% |
|
||||
|
Medium load |
15.5% |
|
||||
|
Low load |
30.3% |
|
||||
|
Light load |
29.1% |
|
||||
|
Medium load |
20.3% |
|
||||
|
Qualcomm |
Dynamic UE-group
Pcell |
Cat 1 |
Medium |
37.5% |
UPT: -14% |
Assumption: Number of Ues changes from 25 to 20 |
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT |
Access delay/latency/UE power consumption/Other KPI(s), if any |
Reference configuration |
Baseline configuration/assumption |
Traffic model/Other evaluation methodology/assumption details/notable settings |
|
CMCC |
SSB/SIB1-less
scheme: |
cat.2 |
Zero |
31.4% |
/ |
CC1 carries SIB1 of CC2, the power consumption of CC1 increases 1.73% for FDM SIB of both CC. |
set 1 |
Baseline
scheme: |
numerical
analysis. |
|
cat.1 |
56.5% |
/ |
CC1 carries SIB1 of CC2, the power consumption of CC1 increases 1.41% for FDM SIB of both CC. |
||||||
|
Huawei,
HiSilicon |
SIB-less on ES CC |
Cat 2 |
0% load(zero) |
33.6% |
N/A |
N/A |
Set 2 |
4 SIB1 with 20ms period,20RB |
FTP3
IM.
|
|
10% load(low) |
26.2% |
N/A |
N/A |
||||||
|
20% load(light) |
19.0% |
N/A |
N/A |
||||||
|
30% load(medium) |
16.0% |
N/A |
N/A |
||||||
|
dual SIB on Anchor CC |
0% load(zero) |
-7.5% |
N/A |
N/A |
|||||
|
10% load(low) |
-6.7% |
N/A |
N/A |
||||||
|
20% load(light) |
-6.1% |
N/A |
N/A |
||||||
|
30% load(medium) |
-5.5% |
N/A |
N/A |
||||||
|
SIB-less on ES CC |
0% load(zero) |
20.2% |
N/A |
N/A |
4 SIB1 with 40ms period,20RB |
||||
|
11.2% |
N/A |
N/A |
4 SIB1 with 80ms period,20RB |
||||||
|
5.9% |
N/A |
N/A |
4 SIB1 with 160ms period,20RB |
||||||
|
10% load(low) |
15.7% |
N/A |
N/A |
4 SIB1 with 40ms period,20RB |
|||||
|
9.3% |
N/A |
N/A |
4 SIB1 with 80ms period,20RB |
||||||
|
4.0% |
N/A |
N/A |
4 SIB1 with 160ms period,20RB |
||||||
|
ZTE,
Sanechips |
(SSB and SIB)-less cell |
1 |
zero |
97.9% 95.4% 91.1% |
|
|
Set 1 |
Baseline: SSB+SIB: {20ms+40ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
FTP3 for Set 1. IM for Set 2. slot-level; Pstatic=P3, η(s_f,s_p )=1; time-domain scaling for SSB; time
and frequency domain scaling for SIB. |
|
low |
64.3% 43.6% 28.0% |
|
|
||||||
|
SIB-less cell |
zero |
19.3% 24.6% 23.5% |
|
|
Baseline: SSB+SIB: {20ms+40ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
15.5% 13.6% 8.8% |
|
|
||||||
|
anchor cell with dual SIB transmission |
zero |
-14.1% -18.9% -18.1% |
|
energy increase for anchor cell with SIB1 transmission for SIB1-less cell |
Baseline: SSB+SIB: {20ms+40ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
-11.6% -10.5% -6.8% |
|
|||||||
|
(SSB and SIB)-less cell |
zero |
98.4% 96.2% 92.6% |
|
|
Set 2 |
Baseline: SSB+SIB: {20ms+20ms, 80ms+80ms,
160ms+160ms} for anchor cell and non-anchor cell; |
|||
|
low |
80.3% 59.4% 42.4% |
|
|
||||||
|
SIB-less cell |
zero |
40.7% 38.4% 37.0% |
|
|
Baseline: SSB+SIB: {20ms+20ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
28.0% 16.0% 11.5% |
|
|
||||||
|
anchor cell with dual SIB transmission |
zero |
-17.6% -12.4% -12.0% |
|
energy increase for anchor cell with SIB1 transmission for SIB1-less cell |
Baseline: SSB+SIB: {20ms+20ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
-17.8% -10.8% -7.7% |
|
|||||||
|
(SSB and SIB)-less cell |
2 |
zero |
85.8% 83.6% 82.8% |
|
|
Set 1 |
Baseline: SSB+SIB: {20ms+40ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||
|
low |
24.5% 13.4% 9.4% |
|
|
||||||
|
SIB-less cell |
zero |
12.1% 7.0% 3.7% |
|
|
Baseline: SSB+SIB: {20ms+40ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
10.8% 6.2% 3.3% |
|
|
||||||
|
anchor cell with dual SIB transmission |
zero |
-8.0% -4.6% -2.4% |
|
energy increase for anchor cell with SIB1 transmission for SIB1-less cell |
Baseline: SSB+SIB: {20ms+40ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
-7.5% -4.3% -2.3% |
|
|||||||
|
(SSB and SIB)-less cell |
zero |
87.5% 82.6% 81.4% |
|
|
Set 2 |
Baseline: SSB+SIB: {20ms+20ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
|||
|
low |
42.9% 23.6% 19.1% |
|
|
||||||
|
SIB-less cell |
zero |
28.2% 9.8% 5.3% |
|
|
Baseline: SSB+SIB: {20ms+20ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
23.9% 8.0% 4.3% |
|
|
||||||
|
anchor cell with dual SIB transmission |
zero |
-14.1% -4.9% -2.6% |
|
energy increase for anchor cell with SIB1 transmission for SIB1-less cell |
Baseline: SSB+SIB: {20ms+20ms,
80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; |
||||
|
low |
-13.8% -4.6% -2.5% |
|
|||||||
|
NOKIA/NSB |
SSB-less at 20 ms period of RO |
CAT2 |
Unloaded/low/light/Medium |
27.5% 26.1% 26.0% 22.7% |
/ 135 Mbps 105 Mbps 74 Mbps |
|
SET 1 |
Intra-band/collocated
cells with non-CA case, consisting of: |
DL-FTP3. |
|
SSB-less at 160 ms period of RO |
Unloaded/low/light/Medium |
51.8% 48.2% 47.3% 43.2% |
/ 85 Mbps 72 Mbps 56 Mbps |
|
|||||
|
SIB1-less at 20 ms period of RO |
Unloaded/low/light/Medium |
43.1% 40.5% 40.1% 36.5% |
/ 132 Mbps 104 Mbps 73 Mbps |
|
|||||
|
SIB1-less at 160 ms period of RO |
Unloaded/low/light/Medium |
53.8% 51.2% 47.3% 43.2% |
/ 84 Mbps 72 Mbps 56 Mbps |
|
|||||
|
SSB&SIB1-less at 20 ms period of RO |
Unloaded/low/light/Medium |
52.7% 50.6% 52.7% 44.4% |
/ 135 Mbps 105 Mbps 74 Mbps |
|
|||||
|
SSB&SIB1-less at 160 ms period of RO |
Unloaded/low/light/Medium |
55.1% 53.1% 54.9% 46.8% |
/ 85 Mbps 72 Mbps 56 Mbps |
|
|||||
|
CATT |
Adaptation of SSB/SIB1 |
Cat 1 |
Low load |
22.0% |
|
|
set1 |
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms; |
FTP3,
inter-arrival time = 200ms, packet size = 0.5Mbytes. |
|
43.4% |
|
|
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms;DTX configuration: gNB starting offset of DTX on locate before UE DRX on duration in order to support UE wakeup; |
||||||
|
Fujitsu |
SSB&SIB-less |
Cat2 |
Zero low light medium |
34.5% 27.0% 21.7% 16.7% |
|
|
Set 1 |
Baseline scheme: 20 ms SSB/SIB1 period |
BS
goes into mico-sleep on symbolc w/o TX/RX |
|
Zero low light medium |
36.0% 24.7% 18.4% 13.5% |
|
|
Set 2 |
|||||
|
Ericsson |
20ms Discovery signal (4 symbols) + no SIB1 |
Cat1 |
Zero |
2.6% / 5.9% |
|
|
Set 1 |
Baseline scheme: 20ms SSB + 160ms SIB1 |
one
SSB/ four SSBs |
|
Qualcomm |
on-demand SIB1 |
Cat 1 |
Empty load |
5.8% / 7.7% / 8.6% |
|
|
Set 1 |
Baseline: 20ms periodicity for
SSB/SIB1/RO, one beam |
|
|
32.1% / 36.6% / 38.8% |
|
|
Baseline: 20ms periodicity for
SSB/SIB1/RO, 8 beams |
|
Observation includes the results for techniques that are also evaluated under #A-6. The following is observed.
In general, for SSB and/or SIB saved from one carrier of two carriers, 8 resources observed BS energy savings gain, by 5.1%~97.4% for empty load, 3.0%~58.4% for low load, and 1.0%~7.9% for light load, 0.3%~5.7% for medium load. When traffic load is low, network may turn off SCell for energy saving. The results are for FR1 only.
With one of two carriers having simplified SSB and no SIB1, one result shows BS energy saving gain can be achieved by 31.4%~56.5% compared with a baseline of both carriers having SSB and SIB1 periodicity of 20ms; the same source company result also show that with CA configured where SIB1 is already carried by PCell, compared with normal SSB on SCell, the gain of simplified SSB on SCell can be 5.7%~10.5%.
With SIB-less only from one of two carriers and SSB is still transmitted,
·
one result shows that
33.6%~16.0% BS energy saving gain can be achieved compared with a carrier has
20ms SIB1 periodicity and both SSB and SIB1
are transmitted, and the gain which decreases
as the traffic load increases, compared with 20ms SIB1 periodicity.
Meanwhile, the SIB1 carried on another carrier increase the energy of that
carrier by 7.5%~5.5%, resulting a total saving across two carries by
26.1%~10.5%. The gain decreases to 4.0% when the baseline SIB1 periodicity
increases to 160ms;
· one result shows BS energy saving gain can be 3.3%~40.7% compared with baseline of SSB+SIB periodicity of {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell; meanwhile, the SIB1 carried on another carrier increase the energy of that carrier by 2.0%~17.8%, resulting a total saving across two carries by 1.3%~22.9%;
· one result shows at different loads, compared to baseline of 20 ms SSB/SIB1 periodicity, that BS energy savings can be achieved by 53.8%~36.5% with RO periodicity of 20ms and 160ms;
· also one result show less than 2.3% BS energy savings when compared with a baseline of SCell having SIB1.
With SSB-less only from one of two
carriers, for CA in which case the SIB is already saved from ScellSCell, with assumption that UE is able to acquire
sync from a carrier from another band,
· at different loads, compared to a baseline of 20 ms SSB/SIB1 periodicity, one result shows BS energy savings by 27.5%~22.7% and 51.8%~43.2% when the RO periodicity is 20ms and 160ms respectively;
· two results show that BS energy savings can be 5.1%~14.7% at different loads, compared to a baseline of 20ms SSB periodicity;
· one result shows with the same load, BS energy saving gain can be 6.1%~15.2% for DL traffic, and 18.7%~39.4% for UL traffic compared with baseline of SSB periodicity of {20ms, 80ms, 160ms}. The BS energy saving gain from SSB-less cell with UL traffic is 12.6%~24.2% larger than SSB-less cell with DL traffic;
· one result also shows that when the baseline Scell SSB periodicity is 160ms, only 0.3%~3% BS energy savings can be achieved, and one another shows BS energy savings by less than 7.9% if compared with Scell having SIB1.
· UE measurement is based on SSB(s) transmitted in the other carrier of the two carriers
With both SSB-less and SIB1-less from one of two carriers for non-CA operation, with assumption that UE is able to acquire sync from a carrier from another band,
· compared to baseline of 20 ms SSB/SIB1 periodicity on both carriers, one result shows BS energy savings by 55.1%~44.4% with RO periodicity of 20ms~160ms at different loads, and one result shows 9.1%~14.8% energy savings at empty load if an anchor carrier carries additional SIB1 for another carrier;
· at different loads, compared to baseline of 20 ms SSB/SIB1 periodicity, one result shows BS energy savings by 36.0%~13.5% when combined with simplified SSB (i.e. PSS and SSS only);
· one result shows that with baseline of SSB+SIB periodicity of {20ms+20ms, 80ms+80ms, 160ms+160ms} for anchor cell and non-anchor cell, BS energy savings can be 9.4%~97.9% if an anchor carrier carries the SSB and SIB1 for another carrier depending on the traffic load. Meanwhile, the SIB1 carried on another carrier increase the energy of that carrier by 2.0%~17.8%, resulting a total saving across two carries by 7.4%~80.1%.
· Comparison with CA is not provided
· UE measurement is not considered
For source results where SSB is not transmitted in SCell, performance impact(s) due to lack of AGC and cell measurement results before SCell access and activation is not provided.
For source results where SSB is not transmitted in neighbour cell, mobility performance impact(s) due to SSB-less operation in neighbour cell(s) is not provided.
In most results for SSB and/or SIB saved from one carrier of two carriers, the UPT is not negatively impacted while one result shows slightly increased UPT. One source shows that the SCell activation delay can also be reduced to 6ms from the baseline.
No negative impact observed on UE power consumption for the above schemes.
Additionally, SSB-less SCell for CA can slightly improve the average EE, reported by one result.
One company showed that UE-group Pcell switching together with Scell dormancy could provide network energy saving by up to 37.5% for two-CC CA scenario with FR1 Set 1. However, UPT degrades by 14% if one Scell goes to dormant state.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for semi-statically configured bandwidth part of UEs within a carrier. The evaluation is performed with different traffic, e.g. medium traffic to light traffic for Set 1, and low traffic to very low traffic for Set 3, and the reduced BW of 80 MHz is applied as NES mode compared with baseline BW of 100 MHz.
Table 6.1.1-x: BS energy savings by BWP adaptation within carrier
|
Company |
BS Category |
Load scenario |
ES gain (%) |
KPI |
Reference configuration |
Baseline configuration/assumption |
|
Samsung |
Cat 1 |
Baseline
traffic: 42.8 % RU |
38.2% |
UPT: 6.05%; Packet latency: 6.44%; Scheduling latency: No increase |
Set1 |
Baseline: full 100MHz with 55 dBm NES mode: 80 MHz with 54 dBm |
|
Cat 2 |
27.8% |
|||||
|
Cat 1 |
Baseline
traffic: 7.5 % RU |
52.2% |
UPT: 14.67%; Packet latency: 17.2%; Scheduling latency: No increase |
|||
|
Cat 2 |
17.6% |
|||||
|
Cat 1 |
Baseline
traffic: 32.1 % |
17.4% |
UPT: 28.24%; Packet latency: 39.4%; Scheduling latency: No increase |
Set3 |
Baseline: full 100MHz with 49 dBm NES mode: 80 MHz with 48 dBm |
|
|
Cat 2 |
17.8% |
One source observed BS energy savings by 17.4%~52.2% at the expense of UPT loss by 28.4%~14.47%, and packet latency increases by 6.44%~39.4% when traffic is reduced compared to corresponding baseline. BWP switching delay is not modelled.
On scheduling latency, no negative impact is observed.
=== end of TP ===
Agreement
=== start of TP ===
The following captures the results for dynamic /(semi)-static adaptation of bandwidth of active BWP.
Table 6.1.1-x: BS energy savings by BW adaptation within BWP
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
KPI |
Baseline configuration/assumption |
|
OPPO [R1-2211458] |
adaptation of bandwidth of active BWP of UEs |
Cat 1 |
low load(RU-10%) |
1.4% |
UPT: 554.74Mbps(-46.8%); Access delay/latency: 9.35ms(+86.3%) |
system BW of 100MHz, 64T: (M, N, P, Mg, Ng, MP, NP,) = (8, 8, 2, 1, 1, 4, 8) |
|
low load(RU-0.2%) |
1.3% |
UPT: 513.43Mbps(-52%); Access delay/latency: 1.78ms(+48.3%) |
||||
|
Intel [R1-2212563] |
intra-carrier BWP adaptation |
Low |
-20.6% |
UPT: Baseline (819.7Mbps), ES (346.8 Mbps); Avg EE (baseline): 5.10; Avg EE (ES): 1.87 |
Baseline: Full
BW |
|
|
-75.4% |
UPT: Baseline
(819.7Mbps), ES (99.4 Mbps); Avg EE (baseline): 5.10; |
Baseline: Full
BW |
||||
|
Light |
-45.9% |
UPT: Baseline
(611.5Mbps), ES (155.2Mbps); Avg EE (baseline): 2.66; |
Baseline: Full
BW |
|||
|
-61.8% |
UPT: Baseline
(611.5Mbps), ES (25.7Mbps); Avg EE (baseline): 2.66 |
Baseline: Full
BW |
||||
|
Medium |
-27.6% |
UPT: Baseline
(457.9Mbps), ES (50.5Mbps); Avg EE (baseline): 1.50 |
Baseline: Full
BW |
|||
|
-13.5% |
UPT: Baseline (457.9Mbps),
ES (12.3Mbps); Avg EE (baseline): 1.50; |
Baseline: Full
BW |
||||
|
CEWiT {R1-xxxx} |
Dynamic adaptation of bandwidth of active BWP of UEs with dynamic indication |
Cat 1 |
Medium |
1.75% |
|
Baseline: Full
BW of 100MHz, 32 ports
|
|
Company |
ES scheme |
BS Category &Reference configuration |
Load scenario |
ES gain (%) |
UPT/latency/UE power/ Other KPIs |
Baseline configuration/assumption |
Evaluation methodology/assumption details/traffic model |
|
MTK |
#TxRU_32 |
Cat 1, Set 1 |
Light |
15.8% |
UPT loss:4.54%; latency increase:4.76%; UE power increase:3.48% |
BS #TxRU 64 |
SLS; DRX (160, 8, 100); FTP3 traffic |
|
Cat 2, Set 1 |
15.8% |
UPT loss:4.54%; latency increase:4.76%; UE power increase:3.48% |
|||||
|
#TxRU_16 |
Cat 1, Set 1 |
19.2% |
UPT loss:16.92%; latency increase:20.36%; UE power increase:14.70% |
||||
|
Cat 2, Set 1 |
22.1% |
UPT loss:16.92%; latency increase:20.36%; UE power increase:14.70% |
|||||
|
#TxRU_8 |
Cat 1, Set 1 |
22.1% |
UPT loss:47.48%; latency increase:90.42%; UE power increase:47.94% |
||||
|
Cat 2, Set 1 |
24.9% |
UPT loss:47.48%; latency increase:90.42%; UE power increase:47.94% |
|||||
|
#TxRU_32 |
Cat 1, Set 1 |
Medium |
25.3% |
UPT loss:6.39%; latency increase:6.83%; UE power increase:4.20% |
|||
|
Cat 2, Set 1 |
26.6% |
UPT loss:6.39%; latency increase:6.83%; UE power increase:4.20% |
|||||
|
#TxRU_16 |
Cat 1, Set 1 |
31.4% |
UPT loss:44.78%; latency increase:81.08%; UE power increase:32.85% |
||||
|
Cat 2, Set 1 |
36.7% |
UPT loss:44.78%; latency increase:81.08%; UE power increase:32.85% |
|||||
|
#TxRU_8 |
Cat 1, Set 1 |
36.0% |
UPT loss:87.08%; latency increase:647.07%; UE power increase:79.99% |
||||
|
Cat 2, Set 1 |
45.2% |
UPT loss:87.08%; latency increase:647.07%; UE power increase:79.99% |
|||||
|
#TxRU_32_PDSCH_PowOffset_-3dB |
Cat 1, Set 1 |
Light |
18.8% |
UPT loss:9.06%; latency increase:9.96%; UE power increase:7.62% |
BS #TxRU 64; PDSCH power offset 0 dB |
SLS; DRX (160, 8, 100); FTP3 traffic model; Single value η (=1) |
|
|
Cat 2, Set 1 |
19.7% |
UPT loss:9.06%; latency increase:9.96%; UE power increase:7.62% |
|||||
|
OPPO |
Dynamic adaptation of spatial elements. |
Cat 1,Set 1 |
low load(RU-10%) |
22.1% |
UPT: 550Mbps(-47.2%); latency: 12.41ms(+147%) |
system BW of 100MHz, 64T: (M, N, P, Mg, Ng, MP, NP,) = (8, 8, 2, 1, 1, 4, 8) |
SLS, 8T: (M, N, P, Mg, Ng, MP, NP,) = (4, 2, 2, 1, 1, 2, 2) is used for evaluation; FTP3 traffic model; A = 0.4 and η=1 |
|
low load(RU-0.2%) |
13.7% |
UPT: 782.56Mbps(-21.2%); latency:1.79ms(+49.1%) |
SLS, 8T: (M, N, P, Mg, Ng, MP, NP,) = (4, 2, 2, 1, 1, 2, 2) is used for ES evaluation,; FTP3 IM traffic model; A = 0.4 and η=1 |
||||
|
Huawei,HiSilicon |
Dynamic TRX adaption with Multiple CSIs |
Cat 2,Set 1 |
10% load(low) |
7.7% |
0% UPT loss |
Dynamic TRX adaption with Single 64T CSI; |
NO C-DRX; Subband based CSI-feedback in every 5 slots; FTP3 IM traffic model; A=0.4; η=1, 0.76 |
|
4.0% |
5% UPT loss |
||||||
|
3.4% |
10% UPT loss |
||||||
|
30% load(medium) |
13.0% |
0% UPT loss |
|||||
|
11.3% |
5% UPT loss |
||||||
|
9.6% |
10% UPT loss |
||||||
|
10% load(low) |
7.5% |
0% UPT loss |
C-DRX with (cycle, on-duration, inactivity timer) = (320, 10, 80) ms; Subband based CSI-feedback in every 5 slots; FTP3 IM traffic model; A=0.4; η=1, 0.76 |
||||
|
30% load(medium) |
10.9% |
0% UPT loss |
|||||
|
Cat 2,Set 2 |
10% load(low) |
7.5% |
0% UPT loss |
NO C-DRX; Subband based CSI-feedback in every 5 slots; FTP3 IM traffic model; A=0.4; η=1, 0.76) |
|||
|
13.2% |
5% UPT loss |
||||||
|
10.2% |
10% UPT loss |
||||||
|
30% load(medium) |
10.3% |
0% UPT loss |
|||||
|
19.2% |
5% UPT loss |
||||||
|
14.8% |
10% UPT loss |
||||||
|
ZTE,Sanechips |
TxRU reduction |
Cat 2, Set 1 |
Low load(RU=8.8%) |
7.8% |
1.5% UPT loss |
Baseline: 64TxRU |
FTP3: 20K packet size;η=1 |
|
TxRU reduction |
Low load(RU=8.8%) |
15.5% |
4.47% UPT loss |
||||
|
TxRU reduction |
Low load(RU=8.8%) |
23.5% |
11.06% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
10.8% |
1.5% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
21.7% |
7.06% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
33.7% |
15.31% UPT loss |
||||
|
TxRU reduction |
medium load(RU=32%) |
12.5% |
3.34% UPT loss |
||||
|
TxRU reduction |
medium load(RU=32%) |
24.6% |
10.44% UPT loss |
||||
|
Dynamic TxRUs adaptation via multi-CSI |
Low load(RU=8.8%) |
27.1% |
0.9% UPT loss |
||||
|
light load(RU=20%) |
28.7% |
1.5% UPT loss |
|||||
|
light load(RU=20%) |
31.3% |
7% UPT loss |
|||||
|
medium load(RU=32%) |
23.8% |
1.17% UPT loss |
|||||
|
TxRU reduction |
Low load(RU=10%) |
5.6% |
6.89% UPT loss |
FTP3: 0.1M packet size,η=1 |
|||
|
TxRU reduction |
Low load(RU=10%) |
11.0% |
18.39% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
9.1% |
6.32% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
18.6% |
14.88% UPT loss |
||||
|
TxRU reduction |
Medium load(RU=40%) |
11.8% |
8.01% UPT loss |
||||
|
TxRU reduction |
Medium load(RU=40%) |
25.0% |
20.88% UPT loss |
||||
|
Dynamic TxRUs adaptation via multi-CSI |
Low load(RU=10%) |
7.6% |
3.1% UPT loss |
||||
|
Low load(RU=10%) |
11.1% |
5.04% UPT loss |
|||||
|
Low load(RU=10%) |
12.7% |
6.03% UPT loss |
|||||
|
light load(RU=20%) |
13.8% |
2.52% UPT loss |
|||||
|
light load(RU=20%) |
16.3% |
4.13% UPT loss |
|||||
|
light load(RU=20%) |
18.7% |
5.15% UPT loss |
|||||
|
light load(RU=20%) |
21.1% |
6.96% UPT loss |
|||||
|
Medium load(RU=40%) |
15.7% |
2.89% UPT loss |
|||||
|
Medium load(RU=40%) |
17.1% |
4.16% UPT loss |
|||||
|
TxRU reduction |
Cat 2, Set 2 |
Low load(RU=5%) |
4.8% |
2.03% UPT loss |
Baseline: 32TxRU |
FTP3: 20K packet size,η=1 |
|
|
TxRU reduction |
Low load(RU=5%) |
9.6% |
5.61% UPT loss |
||||
|
TxRU reduction |
Low load(RU=5%) |
14.8% |
12.5% UPT loss |
||||
|
TxRU reduction |
Low load(RU=11%) |
8.0% |
3.07% UPT loss |
||||
|
TxRU reduction |
Low load(RU=11%) |
15.9% |
9.75% UPT loss |
||||
|
TxRU reduction |
Low load(RU=11%) |
25.3% |
19.36% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
9.6% |
5.19% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
19.7% |
12.87% UPT loss |
||||
|
TxRU reduction |
light load(RU=20%) |
32.1% |
23.931% UPT loss |
||||
|
TxRU reduction |
Low load(RU=5%) |
7.9% |
0.42% UPT loss |
FTP3: 4K packet size, η=1 |
|||
|
TxRU reduction |
Low load(RU=5%) |
15.8% |
1.72% UPT loss |
||||
|
TxRU reduction |
Low load(RU=5%) |
24.3% |
3.54% UPT loss |
||||
|
TxRU reduction |
Low load(RU=13%) |
11.2% |
0.67% UPT loss |
||||
|
TxRU reduction |
Low load(RU=13%) |
22.7% |
1.5% UPT loss |
||||
|
TxRU reduction |
Low load(RU=13%) |
35.0% |
3.84% UPT loss |
||||
|
TxRU reduction |
light load(RU=28%) |
14.0% |
1.86% UPT loss |
||||
|
TxRU reduction |
light load(RU=28%) |
27.8% |
6.16% UPT loss |
||||
|
TxRU reduction |
light load(RU=28%) |
43.4% |
14.15% UPT loss |
||||
|
TxRU reduction |
Medium load(RU=48%) |
14.3% |
5.07% UPT loss |
||||
|
TxRU reduction |
Medium load(RU=48%) |
29.4% |
14.63% UPT loss |
||||
|
Dynamic TxRUs adaptation via multi-CSI |
Low load(RU=5%) |
18.1% |
0.62% UPT loss |
||||
|
Low load(RU=13%) |
23.7% |
0.16% UPT loss |
|||||
|
light load(RU=28%) |
19.4% |
0.74% UPT loss |
|||||
|
Medium load(RU=48%) |
13.7% |
1.01% UPT loss |
|||||
|
Vivo [R1-2211018 |
Dynamic antenna
port adaptation |
Cat 1, Set 1 |
12.38% |
9.4% |
UPT loss:0.36%; latency increase: 0.08%; UE power increase: 0.02% |
Baseline: antenna ports are always 64 |
SLS; No UE DRX; FTP3 traffic model,A=0.4, η=1 |
|
12.57% |
9.4% |
UPT loss:1.98%; latency increase: 2.20%; UE power increase: 0.04% |
|||||
|
15.31% |
6.8% |
UPT loss:12.26%; latency increase: 14.20%; UE power increase: 1.35% |
|||||
|
Cat 2, Set 1 |
12.52% |
8.1% |
UPT loss:2.12%; latency increase: 2.35%; UE power increase: 0.17% |
||||
|
13.16% |
8.1% |
UPT loss:6.48%; latency increase:8.25%; UE power increase:0.45% |
|||||
|
16.42% |
6.7% |
UPT loss:18.50%; latency increase:38.22%; UE power increase:1.96% |
|||||
|
Dynamic antenna port adaptation (between 64 ports and 8 ports) with multi-CSI |
Cat 1, Set 1 |
15.33% |
12.8% |
UPT loss:0.02%; latency increase: 0.05%; UE power increase: 0.01% |
Baseline: antenna ports are always 64 |
SLS; No UE DRX; FTP3 traffic model,A=0.4, η=1 |
|
|
NOKIA/NSB |
Reduced number of TX to 32 |
Cat 2, Set 1 |
Low |
27.6% |
UPT: 163,26 Mbps |
Single cell
operation as per SET1 (64 TRX). |
SLS+Post-processing; FTP3 traffic model; A=0,4; Single value η (=1) |
|
Light |
28.5% |
UPT: 117,64 Mbps |
|||||
|
Medium |
29.5% |
UPT: 75,47 Mbps |
|||||
|
Intel |
Antenna port adaptation |
Cat 1, Set 1 |
Low |
19.1% |
UPT Baseline:
819.7Mbps Avg EE
(baseline): 5.11 |
Baseline: 64Tx
(fixed) |
SLS |
|
27.3% |
UPT Baseline:
819.7Mbps Avg EE
(baseline): 5.11 |
Baseline: 64Tx
(fixed) |
|||||
|
4.5% |
UPT Baseline:
819.7Mbps Avg EE
(baseline): 5.11 |
Baseline: 64Tx
(fixed) |
|||||
|
Light |
25.7% |
UPT Baseline:
611.5Mbps Avg EE
(baseline): 2.67 |
Baseline: 64Tx
(fixed) |
||||
|
35.7% |
UPT Baseline:
611.5Mbps Avg EE
(baseline): 2.67 |
Baseline: 64Tx
(fixed) |
|||||
|
1.9% |
UPT Baseline:
611.5Mbps Avg EE
(baseline): 2.67 |
Baseline: 64Tx (fixed) |
|||||
|
Medium |
29.6% |
UPT Baseline:
457.9Mbps Avg EE
(baseline): 1.5 |
Baseline: 64Tx
(fixed) |
||||
|
41.8% |
UPT Baseline:
457.9Mbps Avg EE
(baseline): 1.5 |
Baseline: 64Tx
(fixed) |
|||||
|
0.0% |
UPT Baseline:
457.9Mbps Avg EE
(baseline): 1.5 |
Baseline: 64Tx
(fixed) |
|||||
|
CATT |
Dynamic adaptation of spatial elements |
Cat 1, Set 1 |
Low load |
6.8% |
UPT loss:0.32% |
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);SSB periodicity 20ms;CSI-RS/TRS 10ms;TxRU= 64. |
SLS; (cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms;CSI-RS/TRS 10ms;dynamic spatial antenna adaptation: gNB dynamic adaptation of the number of TxRU from 64TxRU to 32 TxRU; FTP3 traffic model; A=0.4; η(s_f, s_p)=1. |
|
Light load |
12.2% |
UPT loss:0.62% |
|||||
|
Medium load |
18.0% |
UPT loss:3.8% |
|||||
|
Low load |
6.9% |
UPT loss:1.5% |
SLS; SSB periodicity 20ms;CSI-RS/TRS 10ms;TxRU= 64. |
SLS; No DRX; SSB periodicity 20ms;CSI-RS/TRS 10ms;dynamic spatial antenna adaptation: gNB dynamic adaptation of the number of TxRU from 64TxRU to 32 TxRU; A=0.4; η(s_f, s_p)=1. |
|||
|
Light load |
12.3% |
UPT loss:1.6% |
|||||
|
Medium load |
19.6% |
UPT loss:1.8% |
|||||
|
Fujitsu |
Dynamic TxRU adaptation |
Cat 2, Set 1 |
low |
24.1% |
5.7% average UPT loss |
BS #TxRU=64 |
CSI feedback period = 20ms, feedback delay = 4ms, immediate
antenna adaptation delay FTP3 traffic model; A=0.4; Single value η (=1) |
|
light |
18.6% |
4.1% average UPT loss |
|||||
|
medium |
12.0% |
2.3% average UPT loss |
|||||
|
Cat 2, Set 2 |
low |
26.5% |
0.6% average UPT loss |
BS #TxRU=32 |
|||
|
light |
20.0% |
0.5% average UPT loss |
|||||
|
medium |
12.8% |
0.3% average UPT loss |
|||||
|
Ericsson |
BS #TxRU 32 |
Cat1, Set 1 |
Low |
15.0% |
UPT loss of 1%
for 95-%, |
BS #TxRU 64 |
1 SSB FTP3 traffic model Dynamic switching applied, i.e. adapting number of antennas for energy efficiency in durations when only users in good channel condition are scheduled. Note separate evaluation performed for different number of antennas (i.e. no switching between these settings). |
|
Light |
21.2% |
UPT loss of 3%
for 95-%, |
|||||
|
Medium |
22.4% |
UPT loss of 3%
for 95-%, |
|||||
|
BS #TxRU 16 |
Low |
21.4% |
UPT loss of 3%
for 95-%, |
||||
|
Light |
31.6% |
UPT loss of 6%
for 95-%, |
|||||
|
Medium |
36.6% |
UPT loss of 8%
for 95-%, |
|||||
|
Qualcomm |
#TxRU reduction (64 to 32) |
Cat 1, Set 1 |
Low |
29.4% |
UPT loss at 50%tile: 31%; DL SINR loss at 5% tile: 4.5dB |
BS #TxRU 64 |
FTP3 traffic model |
|
Light |
28.6% |
UPT loss at 50%tile: 30%; DL SINR loss at 5% tile: 6.5dB |
|||||
|
Samsung |
#TxRU reduction (64 to 32) |
Cat 1, Set 1 |
Medium |
28.82% |
UPT loss: 12.97%; latency increase: 16.69% Baseline
traffic: 27.87 % RU |
BS #TxRU 64 |
FR1, Port
adaptation from 64 to 32 TxRU |
|
Light |
25.3% |
UPT loss: 14.70%; latency increase: 16.84%; Baseline
traffic: 14.21 % RU |
|||||
|
Low |
19.47% |
UPT loss: 19.19%; latency increase: 17.46% Baseline
traffic: 3.48 % RU |
|||||
|
Low |
10.93% |
UPT loss: 25.12%; latency increase: 16.66% Baseline
traffic: 1.29 % RU |
|||||
|
#TxRU reduction (32 to 16) |
Cat 1, Set 3 |
Medium |
31.9% |
UPT loss: 10.37%; latency increase: 4.58% Baseline
traffic: 21.69 % RU |
BS #TxRU 32 |
FR2, Port
adaptation from 32 to 16 TxRU |
|
|
Low |
26.8% |
UPT loss: 13.42%; latency increase: 15.54% Baseline
traffic: 7.23 % RU |
|||||
|
#TxRU reduction (32 to 8) |
Cat 1, Set 3 |
Medium |
48.2% |
UPT loss: 7.6%; latency increase: 12.47% Baseline
traffic: 21.69 % RU |
BS #TxRU 32 |
FR2, Port
adaptation from 32 to 8 TxRU |
|
|
Low |
40.5% |
UPT loss: 13.7%; latency increase: 26.4% Baseline traffic:
7.23 % RU |
3 sources show different observations. One source show small BW energy saving gain by 1.3%/1.4% at the expense of about 50% UPT loss and increased access delay/latency by 48.3%/86.3%. One source shows a BW energy saving gain of 1.7%. One source shows BS power consumption increases with BWP size reduction in a carrier and negative energy saving gain in the range -13.5%~ -75.4% is observed, together with significantly reduced UPT, and additionally reduced average EE.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for dynamic adaptation of spatial elements.
Table 6.1.1-x: BS energy savings by adaptation of spatial elements
Use table in section 6.3.1.2 of R1-2212935
12 sources observed that BS energy savings can be achieved, at all loads for different sets of reference configurations with FTP3 for FTP3 IM traffic models, with or without UE C-DRX configuration. The gain depends on whether there is multiple CSI report assistance, the number of antenna ports that can be adapted, the load scenarios, and UPT loss. No performance analysis was provided for broadcast and common channels with dynamic antenna adaptation.
With dynamic/semi-static adaptation of spatial elements,
· One source shows that BS energy saving for UE specific PDSCH for FR1 can be achieved by 3.4%~19.2% with dynamic adaptation and multi-CSI, compared to dynamic adaptation of spatial elements with single CSI report. The UPT loss was observed by less than 10%.
· 2 sources shows that the gain for UE specific PDSCH for FR1 can be 7.6%~31.3% with dynamic adaptation and multi-CSI, compared with no adaptation, with UPT loss of 0.02%~7%.
· 2 sources show that the gain can be 6.7%~26.5% with dynamic adaptation without multi-CSI, compared to no adaptation, with UPT loss of 0.3%~18.5%.
· 9 sources show that the gain can be 4.8%~48.2% with static adaptation without multi-CSI, compared to no adaptation, with UPT loss of 0.02%~87.08%. One source observed that the downlink coverage is reduced by 4.5dB – 6.5dB when reducing the number of TxRUs from 64 to 32 in Set 1 FR1 configuration.
· One source shows that when dynamic antenna adaptation is variably changed, the gain is reduced to a range of 0~4.5% with 0.02%~2.18% UPT loss.
· One source shows BS energy saving can be 18.8%~19.7% that additional gain can be obtained when this scheme is combined with PDSCH power offset. The UPT loss is observed by 9.06%.
· More number of elements are reduced, more gain can be generally obtained.
On latency, there is negative impact observed in three sources and the increment becomes larger as the number of reduced antenna ports becomes larger.
On UE power consumption, 2 sources show that there is increase by up to 79.99% % (number of TX RU is reduced from 64 to 8).
Additionally, one result shows that the average EE can be generally increased except for the low load case where number of antenna is reduced from 64 to 16, and the case of antenna number variably changing.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for TRP muting in multi-TRP operation.
Table 6.1.1-x: BS energy savings by TRP muting in multi-TRP operation
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
UPT/latency/UE power consumption/ Other KPIs |
Baseline configuration/assumption |
Evaluation methodology/assumption details |
|
NOKIA/NSB |
Semi-static reduced number of TRPs |
Cat 2, Set 1 |
Low |
38.8% |
UPT loss: -14.49% |
2
TRPs are assumed. |
SLS+Post-processing, FTP3 traffic model; A=0,4; Single value η (=1). 70% of the P_Static among TRPs |
|
Light |
37.2% |
UPT loss: -14.14% |
|||||
|
Medium |
36.9% |
UPT loss: -7.27% |
|||||
|
CATT |
Dynamic TRP muting/adaptation in multi-TRP operation |
Cat 1, Set 1 |
Low load |
28.4% |
UE power: 50.6; UE ESG:12.7% |
M-TRP configuration: One cell is configured with 2TRPs; Both of TRP are activated. |
SLS; (DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms); SSB periodicity 20ms; CSI-RS/TRS 10ms; TRP OFF: 160ms SSB/CSI-RS transmission. When TRP is activated, additional CSI-RS/TRS is transmitted before data scheduling. FTP3 traffic model; A=0.4; η(s_f, s_p)=1. |
|
Light load |
28.7% |
UE power: 50.6; UE ESG:12.7% |
|||||
|
Medium load |
19.7% |
UE power: 51.6; UE ESG:12.4% |
|||||
|
Qualcomm |
Semi-static TRP reduction (2 to 1) |
Cat 1, Set 1 |
Low |
41.6% |
UPT loss at 50%-tile: 16% |
2 TRPs, each with 64 TxRUs |
FTP3 traffic model |
|
Light |
39.0% |
UPT loss at 50%-tile: 22% |
Based on the results from 3 sources, fFor
two TRP configuration case at different loads,
· (2 sources) with semi-static TRP reduction, BS energy saving gain can be achieved by 36.9%~41.6% compared to no TRP reduction, with UPT loss of 7.27%~22%;
· (one source) with dynamic TRP reduction, compared to no TRP reduction, BS energy saving gain can be achieved by 19.7%~28.7%, without reported UPT impact. It assumes two TRP are always transmitting CSI-RS.
BS energy savings can be achieved by 19.7%~41.6%
for two TRPs configuration at different loads, at the expense of UPT loss.
For the BS energy saving gain around 36.9%~41.6%,
UPT loss is observed by 7.27%~22%.
For the BS energy saving gain around 19.7%~28.7%, it is also observed from one source that UE power savings can be achieved by about 12%.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for adaptation of transmission power of signals and channels.
Table 6.1.1-x: BS energy savings by dynamic transmission power adaptation
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
Baseline configuration/assumption |
Other KPI |
|
MTK |
PDSCH_PowOffset_-3dB |
Cat 1 |
Light |
8.7% |
Baseline：PDSCH power offset 0 dB ES scheme：PDSCH power offset -3/-6/-9 dB reference configuration：Set1 FTP3，DRX (160, 8, 100)，Single value η (=1) |
UPT:2.03%,UE power comsumption:1.80%,ltency:2.07% |
|
PDSCH_PowOffset_-6dB |
11.1% |
UPT:5.66%,UE power comsumption:4.47%,latency:6.00% |
||||
|
PDSCH_PowOffset_-9dB |
9.0% |
UPT:10.80%,UE power comsumption:9.17%,latency:12.11% |
||||
|
PDSCH_PowOffset_-3dB |
Medium |
13.9% |
UPT:3.28%,UE power comsumption:2.46%,latency:3.39% |
|||
|
PDSCH_PowOffset_-6dB |
18.7% |
UPT:8.97%,UE power comsumption:6.80%,latency:9.85% |
||||
|
PDSCH_PowOffset_-9dB |
17.7% |
UPT:19.49%,UE power comsumption:14.78%,latency:24.21% |
||||
|
PDSCH_PowOffset_-3dB |
Cat 2 |
Light |
8.7% |
UPT:2.03%,UE power comsumption:1.80%,latency:2.07% |
||
|
PDSCH_PowOffset_-6dB |
11.8% |
UPT:5.66%,UE power comsumption:4.47%,.latency:6.00% |
||||
|
PDSCH_PowOffset_-9dB |
11.2% |
UPT:10.80%,UE power comsumption:9.17%,latency:12.11% |
||||
|
PDSCH_PowOffset_-3dB |
Medium |
14.7% |
UPT:3.28%,UE power comsumption:2.46%,latency:3.39% |
|||
|
PDSCH_PowOffset_-6dB |
20.6% |
UPT:8.97%,UE power comsumption:6.80%,latency:9.85% |
||||
|
PDSCH_PowOffset_-9dB |
21.0% |
UPT:19.49%,UE power comsumption:14.78%,latency:24.21% |
||||
|
#TxRU_32_PDSCH_PowOffset_-3dB |
Cat 1 |
Light |
18.8% |
Baseline：PDSCH power offset 0 dB,BS #TxRU 64 ES scheme：PDSCH power offset -3 dB, BS #TxRU 32 reference configuration：Set1 FTP3，DRX (160, 8, 100)，Single value η (=1) |
UPT:9.06%,UE power comsumption:7.62%,latency:9.96% |
|
|
Cat 2 |
19.7%
|
UPT:9.06%,UE power comsumption:7.62%,latency:9.96% |
||||
|
Huawei，HiSilicon
|
Dynamic Power back-off with Multiple CSIs
|
Cat 2
|
30% load(medium)
|
5.3% |
baseline: Dynamic Power back-off with Single CSI ES scheme: Dynamic Power back-off with Multiple CSIs reference configuration: Set1 FTP3 IM, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; η=1, 0.76(s_f*s_p<0.5) |
UPT: 0% loss |
|
7.3% |
baseline: Dynamic Power back-off with Single CSI ES scheme: Dynamic Power back-off with Multiple CSIs reference configuration: Set1 VoIP, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; η=1, 0.76(s_f*s_p<0.5) |
|||||
|
6.9% |
baseline: Dynamic Power back-off with Single CSI ES scheme: Dynamic Power back-off with Multiple CSIs reference configuration: Set2 VoIP, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; η=1, 0.76(s_f*s_p<0.5) |
|||||
|
11.5% |
baseline: Dynamic Power back-off with Single CSI ES scheme: Dynamic Power back-off with Multiple CSIs reference configuration: Set2 VoIP, 4T for Set 2,NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; η=1, 0.76(s_f*s_p<0.5) |
|||||
|
5.3% |
baseline: Dynamic Power back-off with Single CSI ES scheme: Dynamic Power back-off with Multiple CSIs reference configuration: Set2 FTP3 IM, 4T for Set 2, NO C-DRX; Subband based CSI-feedback in every 5 slots, slot level with time-domain scaling; A=0.4; η=1, 0.76(s_f*s_p<0.5) |
|||||
|
ZTE,Sanechips
|
PDSCH PSD reduction
|
Cat 2 |
Low load(RU=10%) |
2.3% |
Baseline: 55dBm reference configuration:Set 1: FR1 TDD, FTP3: 20K packet size, slot-level,Pstatic=P3, η=1 |
0.56% UPT loss |
|
light load(RU=20%) |
4.4% |
1.82% UPT loss |
||||
|
Medium load(RU=31%) |
6.0% |
3.8% UPT loss |
||||
|
PDSCH PSD reduction
|
Low load(RU=10%) |
6.4% |
1.26% UPT loss |
|||
|
light load(RU=20%) |
10.1% |
1.83% UPT loss |
||||
|
Medium load(RU=31%) |
12.9% |
2.38% UPT loss |
||||
|
Low load(RU=4.7%) |
3.9% |
Baseline: 55dBm reference configuration:Set 1: FR1 TDD, FTP3: 0.5M packet size, slot-level,Pstatic=P3, η=1 |
5.74% UPT loss |
|||
|
Low load(RU=9.6%) |
7.0% |
4.32% UPT loss |
||||
|
light load(RU=23.5%) |
12.2% |
5.48% UPT loss |
||||
|
Medium load(RU=38.4%)
|
16.6% |
9.81% UPT loss |
||||
|
PDSCH PSD reduction
|
Low load(RU=13%) |
5.9% |
Baseline: 49dBm reference configuration:Set 2: FR1 FDD, FTP3: 0.1M packet size, slot-level,Pstatic=P3, η=1 |
0.64% UPT loss |
||
|
light load(RU=29%) |
8.6% |
0.05% UPT loss |
||||
|
PDSCH PSD reduction
|
Low load(RU=13%) |
11.8% |
1.56% UPT loss |
|||
|
light load(RU=29%) |
17.0% |
0.75% UPT loss |
||||
|
Dynamic PDSCH PSD adaptation via multi-CSI |
Low load(RU=10%) |
12.1% |
Baseline: 55dBm reference configuration:Set 1: FR1 TDD, FTP3: 20K packet size, slot-level,Pstatic=P3, η=1 |
0.38% UPT loss |
||
|
light load(RU=20%) |
16.6% |
0.35% UPT loss |
||||
|
Medium load(RU=31%) |
23.8% |
1.17% UPT loss |
||||
|
Medium load(RU=31%) |
16.4% |
0.27% UPT loss |
||||
|
NOKIA/NSB
|
Reduced DL transmit power by 3dB |
Cat 2 |
Low
|
9.8% |
Baseline: MaximumTx power of 49 dBm.UEs are initially in RRC_CONNECTED state reference configuration:Set 2, DL-FTP3, A=0,4; Single value η (=1) SLS |
UPT:144 Mbps |
|
Reduced DL transmit power by 6dB |
12.2% |
UPT:134 Mbps |
||||
|
Reduced DL transmit power by 9dB |
13.4% |
UPT:119 Mbps |
||||
|
Reduced DL transmit power by 3dB |
Light |
15.4% |
UPT:104 Mbps |
|||
|
Reduced DL transmit power by 6dB |
19.7% |
UPT:97 Mbps |
||||
|
Reduced DL transmit power by 9dB |
17.9% |
UPT:88 Mbps |
||||
|
Reduced DL transmit power by 3dB |
Medium |
16.2% |
UPT:76 Mbps |
|||
|
Reduced DL transmit power by 6dB |
23.4% |
UPT:70 Mbps |
||||
|
Reduced DL transmit power by 9dB |
24.7% |
UPT:63 Mbps |
||||
|
DCM
|
PDSCH_PowOffset_-6dB |
Cat 1 |
Light |
6.6% |
Baseline:PDSCH power offset 0 dB reference configuration:Set 1,FTP3, A=0.4, Single value η (=1) |
1.00% UPT loss |
|
PDSCH_PowOffset_-12dB |
8.3% |
2.60% UPT loss |
||||
|
PDSCH_PowOffset_-18dB |
8.7% |
5.70% UPT loss |
||||
|
PDSCH_PowOffset_-6dB |
Medium |
15.5% |
2.50% UPT loss |
|||
|
PDSCH_PowOffset_-12dB |
19.5% |
2.00% UPT loss |
||||
|
PDSCH_PowOffset_-18dB |
20.4% |
5.80% UPT loss |
||||
|
PDSCH_PowOffset_-6dB |
High |
24.1% |
-3.10% UPT loss |
|||
|
PDSCH_PowOffset_-12dB |
29.9% |
-0.70% UPT loss |
||||
|
PDSCH_PowOffset_-18dB |
31.4% |
0% UPT loss |
||||
|
Intel |
Transmit Power Adaptation/ -12dB power
|
Cat1 |
Low |
19.2% |
Baseline: Full power SLS; No C-DRX used for UEs; CSI feedback based on SRS; SIB1 BW: 48 PRB; No paging overhead; 1 SSB beam; SSB/PRACH periodicity: 20msec; SIB1 periodicity: 40msec; Slot level model For scaling: A = 0.4; η(s_f,s_p )=1 for any sf, sp; |
Baseline: 819.7 Mbps Avg EE (Baseline): 5.10 Avg EE (ES) : 5.43 |
|
Light |
28.2% |
Baseline: 611.5 Mbps Avg EE (Baseline): 2.66 |
||||
|
Medium |
34.3% |
Baseline: 457.9 Mbps Avg EE (Baseline): 1.5 |
||||
|
Transmit Power Adaptation/ -6dB power
|
Low |
17.6% |
Baseline: 819.7 Mbps Avg EE (Baseline): 5.10 |
|||
|
Light |
25.4% |
Baseline: 611.5 Mbps Avg EE (Baseline): 2.66 |
||||
|
Medium |
30.0% |
Baseline: 457.9 Mbps Avg EE (Baseline): 1.5 |
||||
|
CATT |
Adaptation of transmission power of signals and channels
|
Cat 1 |
Low load |
3.9% |
Baseline:SSB periodicity 20ms;CSI-RS/TRS 10ms;Transmission power:55dBm; reference configuration:Set 1, FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes; A=0.4; η(s_f, s_p)=1.
|
UPTloss:1.6% |
|
Light load |
7.7% |
UPTloss:1.8% |
||||
|
Medium load |
9.1% |
UPTloss:2.8% |
||||
|
Low load |
4.1% |
Baseline: SSB periodicity 20ms;CSI-RS/TRS 10ms;(DRX-cycle, on duration timer, inactivity timer) = (160ms, 8ms, 100ms);Power domain adaptation; reference configuration:Set 1, FTP3, inter-arrival time = 200ms, packet size = 0.5Mbytes; A=0.4; η(s_f, s_p)=1.
|
UPTloss:1.9% |
|||
|
Light load |
7.7% |
UPTloss:3.9% |
||||
|
Medium load |
11.2% |
UPTloss:3.1% |
||||
|
Ericsson |
Tx power adaptation (reduction up to 12 dB)
|
Cat1 |
Low |
20.9% |
Baseline: BS Tx power 55 dBm reference configuration:Set 1,FTP3 1 SSB Single value η (=1). For ES scheme: dynamic switching applied, i.e. adapting DL Tx power for energy efficiency in durations when only users in good channel condition are scheduled. Note separate evaluation performed for different power settings (i.e. no switching between these settings) |
UPT loss of 1% for 95-% UE, |
|
Light |
40.5% |
UPT loss of 1% for 95-% UE, |
||||
|
Medium |
47.6% |
UPT loss of 0% for 95-% UE, |
||||
|
Tx power adaptation (reduction up to 6 dB)
|
Low |
17.7% |
UPT loss of 1% for 95-% UE, |
|||
|
Light |
33.0% |
UPT loss of 0% for 95-% UE, |
||||
|
Medium |
38.5% |
UPT loss of 2% for 95-% UE, |
||||
|
Samsung |
Transmission power adaptation
|
Cat 1 |
Reference traffic: 7.5 % RU Reduced traffic: 4.4 % RU |
51.5% |
Baseline: BS Tx power 55 dBm reference configuration:Set 1,FTP3 a static part of power for BS: P_3 |
UPT:10.40%, Packet latency: 24.7% Scheduling latency: No increase |
|
Cat 2 |
17.5% |
UPT:10.40%, Packet latency: 24.7% Scheduling latency: No increase |
||||
|
Qualcomm |
Tx power reduction (55dBm to 52dBm)
|
Cat 1 |
Low |
13.1% |
Baseline: BS BS #TxRU 64 with 55dBm Tx power reference configuration:Set 1,FTP3 |
UPT lsss at 50%-tile: 10%, DL SINR loss at 5% tile: 4dB |
|
Light |
6.6% |
UPT loss at 50%-tile: 16%, DL SINR loss at 5% tile: 3dB |
With transmission power reduction on PDSCH, 10 sources show that it can achieve BS energy savings gain at all load cases for both Set 1 FR1 TDD and Set 2 FR1 FDD including 4Tx BS antenna configuration, for both BS categories with FTP3 or FTP3 IM model, with or without UE C-DRX configuration.
With dynamic power reduction assisted by multi-CSI,
· For UE specific PDSCH in FR1, one source observed BS energy saving gain by 5.3%~11.5%, compared to dynamic power reduction without multi-CSI report; one source observed BS energy savings by 12.1%~23.8%, compared to no power reduction baseline;
· The gain generally increases when the traffic load increases;
· The UPT loss is less than 1.17%.
· No performance analysis was provided for broadcast and common channels with dynamic downlink transmission power adaptation.
With semi-static power reduction of 3~18dB in 6 sources and two other sources, compared to a baseline without power reduction, network energy saving can be achieved by 3.9%~51.6%.
· The gain can increase as the traffic load increases in most cases while one source observed a reduced gain, for BS category 1 with power reduction of 3 dB;
· The UPT loss is observed from 2.03%~19.49%.
One source observed that the latency can be increased by up to 24.21% when the power reduction level is up to 9 dB; one source observed that packet latency can be increased by 24.7% while scheduling delay is not increased.
On UE power consumption, one source shows that less than 10% increment is observed in most cases.
One source also observed that when combined with spatial element reduction, in the case of 3 dB power reduction, the network energy savings can be further increased by about 10%, while together with UPT loss/UE power consumption increase/latency increase of 9.06%/7.62%/9.96% respectively.
One source shows this scheme can increase the average EE. One source observed that the downlink SINR is reduced by 3dB – 4dB when reducing the downlink transmission power from 55dBm to 52dBm in Set 1 FR1 configuration.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results by Channel Aware Tone reservation.
Table 6.1.1-x: BS energy savings by Channel Aware Tone reservation
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
Baseline configuration/assumption |
Other KPI |
Note |
|
Qualcomm |
PA Backoff reduction of 1-3dB due to PAPR reduction from Channel Aware Tone reservation |
Cat 1 |
|
9.5% |
Set 3 |
UPT:0.00% latency: 0% UE power consumption: 0%
|
Evaluation showing utilization of PAPR reduction, where the PAPR reduction is used to reduce the backoff PA attribute (Pmax) while maintaining the TX power and signal EVM
The Backoff also compensates for the tones used for the TR signal, thus no UPT loss occurs
Comparing Channel Aware Tone Reservation to Transparent Tone Reservation Note: η was calculated corresponding to the backoff reduction as was provided by a formula (referencing Tdoc R1-220996) |
|
|
2.1% |
||||||
|
|
4.4% |
Set 1 |
|||||
|
|
2.1% |
It isOne source
observed that channel aware tone reservation can achieve PA back-off reduction
of 1-3 dB which leads to 2.1%~9.5% BS energy saving gains depending on
configurations, compared with transparent tone reservation. Note PA scaling
values used for this NW ES scheme are not covered by RAN1
power consumption scaling model.
On UPT/latency, no negative impact is observed.
No impact on UE power consumption.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results for UE post-distortion.
Table 6.1.1-x: BS energy savings by [UE post-distortion]
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
Baseline configuration/assumption |
Other KPI |
Note |
|
Qualcomm |
UE post-distortion |
Cat 1 |
|
16.1% |
Set 3 |
UPT:0.00% latency: 0% |
Evaluation showing utilization of PAPR reduction, where the PAPR reduction is used to reduce the backoff PA attribute (Pmax) while maintaining the TX power and signal EVM
The Backoff also compensates for the tones used for the TR signal, thus no UPT loss occurs
Processing and power consumption of the UE depends on the UE receiver’s design for DPoD. Note: η was calculated corresponding to the backoff reduction as was provided by a formula (referencing Tdoc R1-220996) |
One source is observed that
UE post-distortion can achieve BS energy saving by 16.1% for Set 3 reference
configuration. Note PA scaling
values used for this NW ES scheme are not covered by RAN1
power consumption scaling model.
On UPT or latency, there is no negative impact observed.
The impact on UE power consumption depends on UE receiver’s design for DPoD.
=== end of TP ===
Agreement
=== start of TP ===
The following capture the results by Over the air DPD.
Table 6.1.1-x: BS energy savings by Over the air DPD
|
Company |
ES scheme |
BS Category |
Load scenario |
ES gain (%) |
Baseline configuration/assumption |
Other KPI |
Note |
|
Qualcomm |
Over the air DPD (DPD-OTA) |
Cat 1 |
|
8.9% |
Set 3 |
UPT:0.00% latency: 0% |
Evaluation showing utilization of PAPR reduction, where the PAPR reduction is used to reduce the backoff PA attribute (Pmax) while maintaining the TX power and signal EVM Note: η was calculated corresponding to the backoff reduction as was provided by a formula (referencing Tdoc R1-220996) |
One source observed that DPD-OTA can achieve BS energy saving by 8.9% for Set 3 reference configuration. Note PA scaling values used for this NW ES scheme are not covered by RAN1 power consumption scaling model.On UPT/latency, no negative impact is observed.
Additional UE power consumption is considered to be negligible due to the low report periodicity expected.
=== end of TP ===
R1-2210852 Network Energy Saving Techniques FUTUREWEI
R1-2210859 On techniques aspects for network energy savings Huawei, HiSilicon
R1-2211019 Discussion on NW energy saving technique vivo
R1-2211086 Discussion on network energy saving techniques Fujitsu
R1-2211098 Network energy saving techniques Nokia, Nokia Shanghai Bell
R1-2211210 Network Energy Saving techniques in time, frequency, and spatial domain CATT
R1-2211242 Discussion on network energy saving techniques Spreadtrum Communications
R1-2211373 Discussions on techniques for network energy saving xiaomi
R1-2211411 Discussion on Network Energy Saving Techniques Intel Corporation
R1-2211459 Discussion on network energy saving techniques OPPO
R1-2211518 Discussion on network energy saving techniques Transsion Holdings
R1-2211532 Discussion on the network energy saving techniques China Telecom
R1-2211598 Discussion on potential network energy saving techniques Panasonic
R1-2211692 Discussion on network energy saving techniques CMCC
R1-2211751 Discussion on network energy saving techniques NEC
R1-2211780 Network energy saving techniques Lenovo
R1-2211821 Discussion on network energy saving techniques Apple
R1-2211846 Potential techniques for network energy saving InterDigital, Inc.
R1-2211904 Discussion on NW energy saving techniques ZTE, Sanechips
R1-2211938 Views on the scope for Rel. 18 network energy saving techniques AT&T
R1-2211995 Discussion on NW energy saving techniques NTT DOCOMO, INC.
R1-2212057 Network energy saving techniques Samsung
R1-2212129 Network energy saving techniques Qualcomm Incorporated
R1-2212155 Network energy savings techniques Ericsson
R1-2212260 Network energy saving techniques MediaTek Inc.
R1-2212302 Discussion on physical layer techniques for network energy savings LG Electronics
R1-2212315 Discussion on network energy saving techniques Rakuten Symphony
R1-2212335 Discussion on potential L1 network energy saving techniques for NR ITRI
R1-2212381 On Network Energy Saving Techniques Fraunhofer IIS, Fraunhofer HHI
R1-2212814 Discussion on Network energy saving techniques CEWiT (rev of R1-2212765, rev of R1-2212429)
R1-2212564 Discussion Summary #1 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
From Nov 14th session
Agreement
The following template is to be used for capturing potential network energy saving techniques into the TR.
6.X.Y Technique A/B/C/D-{number}
[Moderator Note: Rapporteur will numerate the techniques in the TR]
6. X.Y.1 Description of technique
[Moderator Note: background information and general description of the technique are described here. This subsection to be discussed in AI 9.7.2]
6. X.Y.2 Analysis of NW energy saving and performance impact
[Moderator Note: Analysis/Observation of performance evaluations. This subsection to be discussed in AI 9.7.1]
6. X.Y.3 Legacy UE and RAN1 specification impacts
[Moderator Note: any observation of impact to legacy UEs from RAN1 perspective, and any RAN1 specification impact described here. The focus of the specification impact should be from RAN1 perspective. If the technique has sub-techniques that are analyzed in 6.X.Y.2, then legacy UE and RAN1 specification impact should be described for each sub-technique. This subsection to be discussed in AI 9.7.2]
R1-2212565 Discussion Summary #2 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
R1-2212779 Discussion Summary #3 for energy saving techniques of NW energy saving SI Moderator (Intel Corporation)
From Nov 18th session
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.1.X Technique A-1
6.1.X.1 Description of technique
In Rel-15 NR, time-domain positions of transmitted SSBs within a half frame are semi-statically configured. Further, UE assumes a single periodicity for the transmitted SSBs. The transmission of common signal and channels or reception of random-access signals may limit the gNB ability to use (deeper) sleep modes to save energy. Currently, system information (SI) update mechanism can adapt the parameters in the cell, such as those associated with downlink common and broadcast signals, such as SSB/SI/paging/cell common PDCCH, and/or the periodicity/availability of uplink random access resources.
Technique
A-1 adapts the transmission pattern (when applicable) of downlink common
and broadcast signals, such as SSB/SI/paging/cell common PDCCH, and/or the transmission
pattern/availability of uplink random access opportunities. Adaptation
of the transmission pattern includes changes to periodicity, time resource
locations, and omitting of specific signals/channels. The transmission pattern
can be adapted semi-statically or dynamically. For adaptation of
uplink random access opportunities, PRACH resources
configured via SIB1 are used to support legacy and Rel-18 UEs and dynamic
adapted RACH resources are additionally available for Rel-18 UEs.
6.1.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.1.X.3 Legacy UE and RAN1 specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
- The access latency of legacy UEs may be impacted
Specification impact of the technique may include:
For simplified version of SSB, such as only PSS or only PSS and SSS without PBCH, or PSS and SSS with partial PBCH:
- signaling mechanism to inform the UE about the use of simplified version of SSB, if needed,
- Changes to SSB may have impact on SI acquisition, initial access, RRM/RLM measurements, and mobility for legacy UEs and UEs that may not support the technique,
- Technique may be enabled for a carrier only when legacy UEs are not using the carrier.
For skipping of SSB/SIB1 transmission occasion:
- signaling mechanism to inform the UE about the skipping of SSB/SIB transmission occasions, if needed,
- Skipping of common signals and channels, such as SSB and SIB1, may have impact on initial access, RRM/RLM/BM measurements, and performance for legacy UEs and UEs that may not support the technique,
- Technique may be enabled for a carrier only when legacy UEs are not using the carrier.
For configuration/adaptation of longer periodicity of SSB/SIB1 and/or uplink random access opportunities:
- signaling mechanism to inform the UE about the configuration/adaptation,
- Adaption of common signals and channels may have impact on SI acquisition, initial access, RRM/RLM/BM measurements, and performance for legacy UEs and UEs that may not support the technique.
For the paging enhancement where paging resources are grouped in a compact manner, potential specification impact of the enhancements from paging transmission includes the following:
- paging reception procedure (RAN2), i.e., identification of POs and PFs for Rel-18 UEs
- UEs that do not support the technique are expected to follow legacy paging reception procedure in the cell.
For dynamically adapting PRACH periodicity and occasions:
- signaling mechanism to inform the UE about the RACH enhancement resources,
- preparation procedure time for dynamic PRACH adaptation,
- UEs that do not support the technique are expected to use legacy RACH resources in the cell.
For scheduling of SIB1 without PDCCH:
- signaling mechanism to inform the UE about the use of SIB1 without PDCCH, if needed,
- Changes to PDCCH of SIB1 may have impact on initial access, and system information acquisition for legacy UEs and UEs that may not support the technique,
- The
specification impacts may include signalling mechanism to inform the UE about
SIB1 transmissions, details of SI acquisition,.
- Technique may be enabled for a carrier only when legacy UEs are not using the carrier.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.1.X Technique A-2
6.1.X.1 Description of technique
The
semi-static configured UE specific channels/signals may require the gNB to
perform periodic transmission or reception if they are activated. Except for
positioning RS (PRS), the configurations for the listed UE-specific
signals/channels are BWP-specific. Current
specification allows gNB to dynamically activate/deactivate
CG-PUSCH/SPS/CSI-RS/CSI report/SRS using DCI (i.e., PDCCH
transmission) in UE specific manner..
Technique A-2 aims to reduce or omit time occasions for the UE specific resources during low activity/non-active periods of the cell. The potential list of UE specific resources includes periodic/semi-static CSI-RS, group-common/UE-specific PDCCH, SPS PDSCH, PUCCH carrying SR, PUCCH/PUSCH carrying CSI reports, PUCCH carrying HARQ-ACK for SPS, CG-PUSCH, SRS, positioning RS (PRS).
UEs may assist the network with information related to the traffic (e.g., about which resources are necessary or unnecessary) so that the network can optimize its scheduling and achieve more sleep opportunities.
6.1.X.2 Analysis of performance and impacts
No evaluations of this technique are available.
6.1.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include at least:
- mechanisms to
configure and/or inform UEs about the resources
availability,
- UE behavior
and procedures when configuration and/or information of the resource
availability of cell is provided.
Reducing or omitting time occasions for the UE specific resources during low activity/non-active periods of the cell for the UEs that may not support the technique are not expected to impact UEs that do not support the technique.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.1.X Technique A-3
6.1.X.1 Description of technique
Technique A-3 enables for the UE
to send an uplink wake-up signal to request transitioning of a cell from no or
reduced transmission/reception activity to active transmission or reception of
a channel/signal. The technique can be applied to UEs in one or more RRC
states. The
UE wake up signal (WUS) may be used to trigger the SSB/SIB transmission.
Technique A-3 can be used trigger SSB/SIB1
transmissions in A-6. Technique A-3 can be used to trigger gNB to wake
up in A-4.
With the support of WUS, the gNB might be inactive (e.g., where it does not transmit nor receive signal/channel or where it only transmits and receives limited signals). A gNB can transition to become active for transmitting or receiving a channel/signal upon reception of an uplink signal from the UE.
6.1.X.2 Analysis of performance and impacts
6.1.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- design of uplink wakeup signal/channel,
which may be an extension of an existing NR uplink signal/channel,
- signaling details of wakeup signal/channel and if needed, downlink signal/channel design/procedure for carrying information regarding the wakeup configuration,
- conditions for triggering WUS,
- mechanisms for DL synchronization and UE measurements needed prior to WUS transmission,
- UE’s assistance information to aid wake up operations by gNB,
- UE behavior/procedure after transmitting WUS,
- gNB
behavior/procedure after receiving WUS, if need to be specified,
- mechanism on how the UE can be informed about cell activity or lack of activity.
Legacy UEs and UEs that do not support this technique cannot wake up a cell that is inactive. Legacy UEs and UEs that do not support this technique are not provided with expected transmission from the cell, they cannot be operate in the cell.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.1.X Technique A-4
6.1.X.1 Description of technique
Currently, the gNB can use reduce downlink
transmission/uplink reception activity without an explicit cell DTX/DRX pattern
with
restrictions due to UE DRX configurations and any configured
transmission/reception, e.g., common channels/signals. Currently C-DRX is
configured per UE. The alignment of the DRX cycles or offsets for different UEs can be
done only via RRC. During UE DRX off period, the UE does not expect to monitor
PDCCH, but it is allowed to initiate UL transmission according to the
configured resources (e.g. using PUCCH, RACH, SR, or CG-PUSCH).
Aligning/Omitting of DRX patterns across multiple UE’s can be achieved via gNB
implementation. In addition, UE expects to monitor/receive
configured DL signals/channels and network is expected to monitor/receive
configured UL signals/channels, which may prevent the cell DTX/DRX.
Technique A-4 aims at providing mechanisms informing UE whether the cell stays inactive. This may include enhancements to UE DRX configuration, e.g., to align/omit DRX cycles or start offsets of DRX, for UEs in connected mode or idle/inactive mode, potentially allowing longer opportunities for cell inactivity. During a cell DTX/DRX, the cell may have no transmission/reception or only keep limited transmission/reception. For example, the cell does not need to transmit or receive some periodic signals/channels, such as common channels/signals or UE specific signals/channels.
6.1.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.1.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- design of cell DTX/DRX pattern/timers/parameters/procedure, if needed,
- configuration and indication of cell DTX/DRX information to UE, if needed and applicable,
- UE behaviors and procedures when cell DTX/DRX is in operation and/or when UE DRX is configured, if needed,
- potential channel/signal
design and mechanism and uplink procedure (e.g., UE request or assistance
feedback) related to cell DTX/DRX,.
- enhancements to UE DRX configuration.
- enhancements to UE DRX parameter adaptation.
For the cell DTX/DRX cases, depending on DTX/DRX occasions, legacy UEs and UEs that do not support the technique may not have impact to idle/inactive/connected mode operations. For example, if DTX/DRX are not applied to common signals and channel required for idle/inactive/connected modes or applied in UE specific manner, legacy UEs and UEs that do not support the technique may not be impacted.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.2.X Technique B-2
6.2.X.1 Description of technique
In Rel-17, UE-specific BWP configuration and switching is supported. For SPS PDSCH reception, type-2 CG PUSCH transmission, and SP-CSI reporting on PUSCH, once BWP is switched, they should be reactivated by activation DCI.
Technique B-2 supports enhancements to enable UE group-common or cell-specific BWP configuration and/or switching. Also supports enhancements to enable SPS PDSCH reception/Type-2 CG PUSCH transmission/SP-CSI reporting on PUSCH without reactivation after the BWP switching.
6.2.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.2.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- signaling and procedure to support UE group-common or cell-specific BWP configuration and/or switching of BWP,
Legacy UEs and UEs that do not support the technique are not able to change the BWP using the enhanced signaling mechanisms.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.2.X Technique B-3
6.2.X.1 Description of technique
Currently, a bandwidth of a BWP is semi-statically configured, and the bandwidth of the given BWP cannot be dynamically changed. The current BWP framework allows the UEs to be configured with a default BWP and switching to a default BWP based on timer. Reduction of the frequency resources within a BWP can be achieved via configuration and scheduling a the gNB.
Technique B-3 supports enhancements to enable group-common signaling to adapt the bandwidth of active BWP and continue operating in same BWP. Some frequency resources within the active BWP may be deactivated.
6.2.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.2.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- include behavior, procedure, and signaling related to enabling group-common adaptation of the bandwidth of active BWP,
-
It
was noted by companies that reduction of frequency resources with BWP can be
achieved without specification impact, e.g. scheduling limited number of RBs
for a given configured BWP.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.3.X Technique C-1
6.3.X.1 Description of technique
According to legacy MIMO procedures, the adaptation of spatial elements can be achieved by RRC (re-)configurations updating, such as CSI-RS (re-)configurations, in a semi-static manner. Moreover, the current framework allows UE to be configured with multiple CSI-RS resources, where these CSI-RS configurations may be with respect to different numbers of spatial antenna ports or antenna elements. With CSI reports respect to different number of spatial elements available, gNB is able to dynamically adjust the number of spatial elements for PDSCH transmission in current specification. CSI-RS and CSI reporting configurations are BWP-specific, and BWP adaptation framework can be utilized for the adaptation for a UE capable of multiple BWPs and dynamic BWP switching.
Indication for potential enhancements related to spatial element adaptation may help the UEs to adapt the already configured CSI-RS configuration such as dynamic/semi-persistent ON-OFF of CSI-RS or to reconfigure the CSI-RS configuration, with respect to adapted number of spatial elements/ports.
Technique C-1 aims to enhance dynamically adaptation of spatial elements such as the number of active transceiver chains or the number of active antenna panels at gNB in transmitting and/or receiving channels and signals.
6.3.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.3.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- mechanisms to indicate spatial element adaptation to the UE,
- signaling to update the active CSI-RS configurations
- enhancements on CSI-RS (re)configuration, CSI/RRM/RLM measurements, CSI reporting (e.g., multiple CSI reports), and beam management for gNB to switch between different spatial domain configurations,
-- associated UE behavior in case of spatial element adaptation occurs, if needed, e.g., measurements, CSI feedback, power control, PUSCH/PDSCH repetition, SRS transmission, TCI configuration, beam management, beam failure recovery, radio link monitoring, cell (re)selection, handover, initial access, etc.
There is no impact for legacy UEs if the spatial element adaptation is used on a UE-specific basis, i.e., applied only for UEs supporting the technique.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.3.X Technique C-2
6.3.X.1 Description of technique
Technique C-2 aims to support TRP activation/deactivation that can be informed to the UE when a UE is configured with multiple TRPs. The technique aims to dynamically adapt the number of TRPs transmitting and/or receiving signals and channels.
6.3.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.3.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- UE-specific/group-level/cell common signaling for indicating adaptation of TRPs and TRP-related parameters (e.g. TRP index or CORESET pool index) in mTRP,
- enhancements to UE behaviors due to dynamic adaptation of TRPs, e.g., measurements, CSI feedback, power control, PDCCH/PUCCH/PUSCH/PDSCH repetition, single-DCI based scheduling, multi-DCI based scheduling, SRS transmission, TCI configuration, beam management, beam failure recovery, radio link monitoring, cell (re)selection, handover, initial access, etc,
There is no impact for legacy UEs if the spatial element adaptation is used on a UE-specific basis, i.e., applied only for UEs supporting the technique.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.4.X Technique D-1
6.4.X.1 Description of technique
As per current specification, the SSB reference power, ss-PBCH-BlockPower is defined in SIB1. The powercontrolOffsetSS that is the power offset between (NZP)CSI-RS and SSB and the powerControlOffset that is the power offset of PDSCH and (NZP) CSI-RS are semi-statically configured via RRC signaling. The power offset configurations for PDSCH and CSI-RS are BWP-specific. Current specification allows gNB to adapt the PDSCH transmission power..
Technique D-1 aims at adapting the transmission power or PSD of downlink signals and channels dynamically, by enhancing the related configuration to the UE (e.g. considering power offsets that account for potential power adaptation) and/or enhancing the UE feedback (e.g. CSI report) to assist NW energy saving operation. The technique may be applicable to one or more of PDSCH, CSI-RS, DMRS, broadcast channels/signals (e.g., SSB/SI/paging). Enhancements for updating the power offset values between various signals and channels, e.g., CSI-RS to SSB, or PDSCH to CSI-RS using lower layer signaling.
6.4.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.4.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- signaling of modified power of SSB or power ratio between CSI-RS and PDSCH/SSB to provide adaptation of power ratio values, e.g. by utilizing UE-specific, group-level or cell common signaling,
- enhancements on RRM measurements, beam management, beam failure recovery, radio link monitoring, cell (re)selection and handover procedure
- enhancements to CSI measurements and reporting, e.g. multiple CSI reports in a single report
There is no impact for legacy UEs and UEs that do not support the technique if the signaling of modified power ratio between CSI-RS and PDSCH/SSB or between SSB and CSI-RS, enhancements on CSI measurement and reporting are used on a UE-specific basis, i.e., applied only for UEs supporting the enhancement.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.4.X Technique D-2
6.4.X.1 Description of technique
gNB may implement digital pre-distortion (DPD) to compensate for the non-linear impairments of the transmitter in standard transparent manner.
Technique D-2 supports over the air digital pre-distortion at the gNB. In gNB digital pre-distortion over the air, the UEs assist the gNB in reducing nonlinear impairments introduced by the PA, by processing on training signals, and reporting the information needed for gNB digital pre-distortion.
6.4.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.4.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
-
signaling/configuration for supporting gNB digital pre-distortion,
e.g., UE capability, list of non-linear kernels, enhanced CSI-RS,
-
introduction of training signals/CSI-RS enhancements, e.g., high power low
PAPR transmission, rate matching around additional bandwidth spanned by CSI-RS,
- signaling for reporting assistance information for gNB digital pre-distortion,
- indication to the UE of whether it needs to apply non-linear equalization for a transmission
Legacy UEs and UEs that do not support providing assistance information for gNB digital pre-distortion (DPD) may not be able to contribute to improvement of the DPD.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.4.X Technique D-3
6.4.X.1 Description of technique
Technique D-3 supports tone reservation that decreases PAPR, potentially taking into account channel conditions and characteristics. Tone reservation (TR) exploits the channel nulls to carry TR tones, potentially taking into account channel conditions and characteristics. The UE must be notified of the sub-carriers carrying the TR signal for rate matching purposes only if UE performs transmission or reception of the resource including sub-carriers carrying the TR signal.
gNB may be able to implement PAPR reduction in including tone reservations via implementation with appropriate scheduling of signals and channels.
6.4.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.4.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- assistance information from the UE to help gNB determine tone reservation positions,
- mechanism to convey information about tone reservation positions to the UE,
- behaviors associated with handling of resources with tone reservation positions.
Legacy UEs and UEs that do not support the technique may not be aware of tone reservation positions.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.4.X Technique D-4
6.4.X.1 Description of technique
In case of low load, the PA can adapt/reduce its backoff reducing thus the PA power consumption. PA backoff impacts unwanted in-band and out-of-band emissions. gNB may be able to implement PA backoff adaptation in a specification transparent manner.
Technique
D-4 supports modification and/or reduction of the power amplifier (PA) input
bias backoff in cases of no or low load. This technique aims
to enables PA backoff adaptation for few msec, or
usec, and coordinate PA backoff adaptation among neighboring
cells.
6.4.X.2 Analysis of performance and impacts
No evaluations of this technique are available.
6.4.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- enhancements to UE measurements for assessing the impact from the PA backoff adaptation of neighbor cells
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.4.X Technique D-5
6.4.X.1 Description of technique
Technique D-5 supports the UE performing received signal post-distortion processing (e.g. non-linear equalization stage that will “invert” the non-linearity) to combat non-linear impairments from the transmitter. The technique also considers enhancements to transmission of reference signals or information to aid the UE to perform post-distortion processing.
6.4.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.4.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- mechanism and signalling to enable operation of UE post distortion,
- enhancements to reference signals to aid UE post distortion,
- signaling/configuration
for supporting UE digital post-distortion,
(e.g., UEs capability, list of power amplifier models)
- introduction
of activation of UE post distortion, and notification
of selected power amplifier model, and possibly configuration of training
reference signals,
- signaling for indicating to the UE of whether it needs to apply non-linear equalization for a downlink transmission.
Legacy UEs and UEs that do not support the technique are not able to compensate the received signal distortions based on this enhancement mechanism.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.1.X Technique A-6
6.1.X.1 Description of technique
Current specification supports SSB/SIB1-less operation for intra-band CA, where UE retrieves system information from and can perform synchronization based on another intra-band cell that transmits SSB and SIB1. Current specification supports SSB periodicity configuration up to 160 msec.
For technique A-6, the UE may obtain system information from other associated carriers/cells and synchronize from other associated carriers/cells and/or synchronize from signal(s) transmitted on the cell.
Technique A-6 also supports on-demand SSBs/SIB1 transmissions and enable longer periods of cell inactivity to achieve network energy saving. SSB/SIB1 transmission at the serving cell can be triggered on-demand, e.g by the UE.
6.1.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.1.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
Specification impact of the technique may include:
- channel/signal design and behaviors and procedures of on-demand SSBs/SIB1 and any related signaling,
- random access related enhancement including procedures and configuration for UEs to access the SSB/SIB1-less carrier/cell,
- mobility support or paging for the cell that does not transmit SSB and/or SIB1,
- design for new signal/channel (if any) and related procedures,
For on-demand SSB, if no SSB or simplified SSB is transmitted and normal SSB transmission is triggered upon reception of UE WUS, legacy UEs and UEs that do not support this technique may not be able to operate in this cell.
- Technique may be enabled for a carrier only when legacy UEs are not using the carrier.
For on-demand SIB1, if no SIB1 is transmitted and normal SIB1 transmission is triggered upon reception of UE WUS, legacy UEs and UEs that do not support this technique may not be able to operate in this cell.
- Technique may be enabled for a carrier only when legacy UEs are not using the carrier.
For technique where UE may obtain system information from other associated carriers/cells, cell without a SSB cannot be used as Pcell/PScell/inter-band Scell for legacy UEs and UEs that do not support this technique.
For technique where UE may obtain system information from other associated carriers/cells, cell without a SIB1 cannot be used as Pcell for legacy UEs and UEs that do not support this technique.
==== end of TP ====
Agreement
· Agree to following text for inclusion into TR.
==== start of TP ====
6.2.X Technique B-1
6.2.X.1 Description of technique
Intra-band SSB-less Scell operation is supported by the current specification. Pcell switching is supported by handover command according to current specification.
Technique B-1 supports inter-band CA with SSB-less Scell. No SSB transmission in some inter-band SCell. The synchronization is acquired from other cell with SSB transmission or same cell with simplified signal transmission, also in order for fast activation and deactivation of SCell. Enabling of inter-band SSB-less Scell operation that may include mechanism for UE/gNB to trigger normal SSB transmission and/or reference signals, if needed, on a SCell for fast access, where the on-demand uplink triggering signal can be received either at inter-band SSB-less cell or another carrier/cell. RACH transmission opportunity may be supported in SSB-less Scell.
Technique B-1 supports dynamic Pcell switching in which a common primary cell may be dynamically indicated for a group of UEs.
6.2.X.2 Analysis of performance and impacts
[Editor Note: Analysis/Observation of performance evaluations to be discussed in AI 9.7.1]
6.2.X.3 Legacy UE and RAN1 Specification impacts
The list of UE and RAN1 specification impact described in this section is not an exhaustive list. RAN1 may identify additional impact and also determine that listed impact below may no longer apply to the described technique(s) as specification is further developed.
For SSB-less inter-band CA, Specification impact of the technique may include:
- RACH procedures in SSB-less SCell for inter-band CA,
- enhancement on SCell activation procedure,
- enhancements on SCell dormancy operation,
- design for new simplified signal/channel (if supported) and related procedures,
Legacy UEs or UEs that do not support this feature may not be able to operate inter-band CA with SSB-less Scells. A carrier without SSB cannot be operated as a PCell for legacy UEs. The carrier cannot be operated as an SCell for legacy UEs if another intra-band carrier with SSB is not present. At least the feasibility and/or potential requirements of acquiring synchronization/measurements (including AGC aspects) from other cell with SSB transmission in inter-band CA needs study.
For inter-band SSB-less technique, cell without a SSB cannot be used as Pcell/PScell/inter-band Scell for the legacy UEs and UEs that do not support this technique.
For UE-group Pcell switching, specification impact may include:
- mechanism to signal Pcell switching,
- UE behavior based on indicated signalling.
==== end of TP ====
Final summary in R1-2212780.
Please refer to RP-223540 for detailed scope of the WI.
[112-R18-NES] – Yi (Huawei)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2300133 WI Work plan for R18 network energy savings Rapporteur (Huawei)
R1-2300405 Considerations on Network energy savings for NR KT Corp.
R1-2301717 Addition of abbreviations and symbols to TR 38.864 Huawei
From Monday session: As TR is now under change control, prepare corresponding CR.
From Friday session
Agreement
The TP in R1-2301717 for TR38.864 is endorsed. Final CR (Rel-17, TR38.864, CR0001, Cat F) is agreed in R1-2302234.
R1-2300065 Spatial and Power Adaptations for Network Energy Savings FUTUREWEI
R1-2300073 Power saving techniques in spatial and power domains Huawei, HiSilicon
R1-2300143 Techniques in spatial and power domains Nokia, Nokia Shanghai Bell
R1-2300230 Discussion on NES techniques in spatial and power domains Spreadtrum Communications
R1-2300264 Discussion on techniques in spatial and power domains OPPO
R1-2300360 Spatial and power domain adaptation for network energy saving Panasonic
R1-2300372 Discussion on NES techniques in spatial and power domains ZTE, Sanechips
R1-2300403 Network Energy Saving in Spatial and Power Domain Google
R1-2300465 Discussions on NES techniques in spatial and power domain vivo
R1-2300587 Discussion on techniques in spatial and power domains Xiaomi
R1-2300692 Network Energy Saving techniques in spatial and power domain CATT
R1-2300722 Discussion on NES techniques in spatial and power domains China Telecom
R1-2300752 Discussion on NW energy saving techniques in spatial and power domains Fujitsu
R1-2300768 Discussion on network energy saving techniques in spatial and power domains NEC
R1-2300784 Discussion on techniques in spatial and power domains InterDigital Communications
R1-2300960 Discussion on NWES techniques in spatial and power domain Intel Corporation
R1-2301014 Discussion on network energy saving techniques in spatial and power domains CMCC
R1-2301047 Network energy saving techniques in spatial domain ETRI
R1-2301107 Discussion on NES techniques in spatial and power domains LG Electronics
R1-2301163 Spatial Domain Adaptation for NES Fraunhofer IIS, Fraunhofer HHI
R1-2301206 Network energy saving techniques in spatial and power domains Lenovo
R1-2301222 Network energy savings techniques in spatial and power domains AT&T
R1-2301276 Techniques in spatial and power domains Samsung
R1-2301310 Discussion of NES techniques in spatial domain and power domain Transsion Holdings
R1-2301319 Discussion on techniques in spatial and power domains ITRI
R1-2301358 Discussion on spatial and power domain enhancements to support network energy saving Apple
R1-2301425 Techniques in spatial and power domains Qualcomm Incorporated
R1-2301505 Discussion on spatial and power domain enhancements for NW energy savings NTT DOCOMO, INC.
R1-2301554 NW energy saving techniques in spatial and power domains Ericsson
R1-2301599 On NW energy saving techniques in spatial and power domains MediaTek Inc.
R1-2301698 Discussion on spatial and power adaptations for network energy saving CEWiT, Reliance Jio
R1-2301964 FL summary#1 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From Monday session
Agreement
For the purpose of further discussions in RAN1 on NES spatial domain adaptations, consider the following cases
· Type 1: all antenna elements associated to a logical antenna port is disabled/enabled
· Type 2: part/subset of antenna elements associated to a logical antenna port is disabled/enabled
R1-2301965 FL summary#2 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From Tuesday session
Agreement
For spatial element adaptation, further study the following
Agreement
For spatial element adaptation, further study the following
R1-2301966 FL summary#3 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From Thursday session
Agreement
For spatial domain adaptation, further study necessary enhancements for multiple CSI(s) where each CSI corresponds to a spatial adaptation pattern, e.g.
· FFS: gNB indicates to UE which CSI(s) the UE shall report
· FFS: the UE selects which CSI(s) are reported
· FFS: multiple CSI(s) are reported in a joint CSI report
· FFS: Overhead reduction for multiple CSI(s)
Note: UE complexity needs to be taken into account.
Agreement
For adaptation of power offset values between PDSCH and CSI-RS, further study the following
Agreement
For spatial and power domain adaptation, solution(s) based on adaptation within an active BWP is considered as baseline.
Agreement
Discuss the signalling aspects for spatial/power domain adaptation for Rel-18 NES-capable UEs considering that
· Whether there is a need for transition time per adaptation (for UE)
·
Whether/How to inform UE on spatial
adaptation pattern update and/or PDSCH/CSI-RS transmission power change due to
adaptation.
Final summary in R1-2302179.
R1-2300066 Enhancements on cell DTXDRX for NES FUTUREWEI
R1-2300074 Cell DTX/DRX mechanism for network energy saving Huawei, HiSilicon
R1-2300144 Enhancements on cell DTX/DRX mechanism Nokia, Nokia Shanghai Bell
R1-2300231 Discussion on enhancements on cell DTX/DRX mechanism Spreadtrum Communications
R1-2300265 Discussion on enhancements on cell DTX/DRX mechanism OPPO
R1-2300361 Cell DTX/DRX enhancement for network energy saving Panasonic
R1-2300373 Discussion on cell DTX/DRX ZTE, Sanechips
R1-2300404 Network Energy Saving on Cell DTX and DRX Google
R1-2300466 Discussions on enhancements on cell DTX/DRX mechanism vivo
R1-2300588 Discussions on cell DTX-DRX for network energy saving xiaomi
R1-2300693 DTX/DRX for network Energy Saving CATT
R1-2300723 Discussion on cell DTX/DRX mechanism China Telecom
R1-2300753 Discussion on cell DTX/DRX mechanism Fujitsu
R1-2300764 Cell DTX/DRX Configuration for Network Energy Saving NEC
R1-2300785 Discussion on enhancements on cell DTX/DRX mechanism InterDigital Communications
R1-2300961 Discussion on enhancements on cell DTX/DRX mechanism Intel Corporation
R1-2301015 Discussion on cell DTX/DRX enhancements CMCC
R1-2301048 Enhancements on cell DTX/DRX mechanism ETRI
R1-2301108 Discussion on cell DTX/DRX mechanism LG Electronics
R1-2301162 Discussion on cell DTX/DRX mechanism Rakuten Mobile, Inc
R1-2301164 RAN1 Considerations for Cell DTX and DRX Fraunhofer IIS, Fraunhofer HHI
R1-2301277 Enhancements on cell DTX/DRX mechanism Samsung
R1-2301311 Discussion on Enhancement on cell DTX DRX mechanism Transsion Holdings
R1-2301320 Discussion on potential enhancements on cell DTX/DRX mechanism for NR ITRI
R1-2301359 Discussion on UE behavior for cell DRX/DTX Apple
R1-2301426 Enhancements on cell DTX and DRX mechanism Qualcomm Incorporated
R1-2301506 Discussion on enhancements on Cell DTX/DRX mechanism NTT DOCOMO, INC.
R1-2301555 RAN1 aspects of cell DTX/DRX Ericsson
R1-2301600 On NW energy saving enhancements for cell DTX/DRX mechanism MediaTek Inc.
R1-2301699 Discussion on cell DTX/DRX mechanism for network energy saving CEWiT, Reliance Jio
R1-2301814 Summary of issues for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
R1-2301815 Discussion Summary #1 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Thursday session
Agreement
R1-2302131 Discussion Summary #2 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Friday summary
Agreement
At least the following candidate signals/channels for connected mode UEs, which the UE may be expected to not transmit or receive during non-active periods of cell DTX/DRX, are considered from RAN1 perspective for further discussion. The exact set of signals/channels that the UE may be expected to not transmit or receive is FFS.
Other signals/channels are not precluded
Final summary in R1-2302218.
Please refer to RP-230566 for detailed scope of the WI.
R1-2302333 Spatial and Power Adaptations for Network Energy Savings FUTUREWEI
R1-2303955 CSI enhancements for network energy saving Huawei, HiSilicon (rev of R1-2302337)
R1-2302389 Spatial and power domain adaptation for network energy saving Panasonic
R1-2302393 Techniques in spatial and power domains Nokia, Nokia Shanghai Bell
R1-2303910 Discussions on NES techniques in spatial and power domain vivo (rev of R1-2302498)
R1-2302561 Discussion on techniques in spatial and power domains OPPO
R1-2302613 Discussion on NES techniques in spatial and power domains Spreadtrum Communications
R1-2302716 Network Energy Saving techniques in spatial and power domain CATT
R1-2302751 Discussion on network energy saving techniques in spatial and power domains NEC
R1-2302809 Discussion on NWES techniques in spatial and power domain Intel Corporation
R1-2302912 Discussion on NW energy saving techniques in spatial and power domains Fujitsu
R1-2303985 Discussion on NES techniques in spatial and power domains ZTE, Sanechips (rev of R1-2302944)
R1-2302995 Discussion on techniques in spatial and power domains Xiaomi
R1-2303024 Discussion on techniques in spatial and power domains InterDigital, Inc.
R1-2303030 Discussion on spatial/power domain adaptation for network energy saving China Telecom
R1-2303056 Network Energy Saving in Spatial and Power Domain Google
R1-2303141 Techniques in spatial and power domains Samsung
R1-2303202 Network energy saving techniques in spatial and power domains ETRI
R1-2303247 Discussion on network energy saving techniques in spatial and power domains CMCC
R1-2303309 Discussion on spatial and power adaptations for network energy savings CEWiT
R1-2303344 On NW energy saving techniques in spatial and power domains MediaTek Inc.
R1-2303379 Discussion of NES techniques in spatial domain and power domain Transsion Holdings
R1-2303426 Discussion on NES techniques in spatial and power domains LG Electronics
R1-2303496 Discussion on spatial and power domain enhancements to support network energy saving Apple
R1-2303531 Network energy saving techniques in spatial and power domains Lenovo
R1-2303603 Techniques in spatial and power domains Qualcomm Incorporated
R1-2303651 Network energy savings techniques in spatial and power domains AT&T
R1-2303722 Discussion on spatial and power domain enhancements for NW energy savings NTT DOCOMO, INC.
R1-2303757 NW energy saving techniques in spatial and power domains Ericsson
R1-2303780 Discussion on techniques in spatial and power domains ITRI
R1-2303813 Spatial Domain Adaptation for NES Fraunhofer IIS, Fraunhofer HHI
R1-2303850 Discussion on spatial domain adaptation for NES KT Corp.
[112bis-e-R18-NES-01] – Yi (Huawei)
Email discussion on techniques in spatial and power domains by April 26th
- Check points: April 21, April 26
R1-2303913 FL summary#1 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From April 17th GTW session
Agreement
Define necessary enhancements to support both types of spatial adaptation cases (as defined in RAN1#112) in Rel-18.
· Note: This does not imply explicit definition in specifications for adaptation types.
· Note: This does not imply explicit specification changes are made for both cases
Agreement (modified as shown in April 19th GTW session)
Support configurability of NZP CSI-RS resource(s) for channel measurement within one resource setting corresponding to more than one spatial adaptation patterns with at least one of the following
R1-2303914 FL summary#2 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From April 19th GTW session
Agreement
At least support A2-2, i.e. one CSI report configuration contains multiple CSI report sub-configurations where each sub-configuration corresponds to one spatial adaptation pattern.
· FFS: impact on CSI processing requirement
Agreement (further modified as shown in red on April 21st GTW session, in blue on April 26th GTW session)
For a CSI
report config with L sub-configuration(s), support a framework that enables
a UE to report N CSI(s) in one reporting instance where the N
CSI(s) are associated with N sub-configuration(s) from L (where 
) and each CSI corresponds to one sub-configuration.
· For discussion purpose, N=1 refers to single-CSI while N>1 refers to multi-CSI.
· For Semi-persistent/Aperiodic CSI reporting, support gNB trigger/indicate/activate report of N≤L CSIs where N>=1
· The maximum value of N and L are subject to UE capability
· Further study how to address/minimize additional UE complexity
The following bullet was objected by not agreed due to objection from Apple and vivo
· For Periodic CSI reporting, at least the case of N=L is supported where N>=1
Conclusion
New CSI-RS resource (RE mapping) pattern is not introduced for R18 network energy savings purpose.
· Note: CSI-RS resource (RE mapping) pattern above refers to a row in TS 38.211 Table 7.4.1.5.3-1 determining CSI-RS locations within a slot.
Agreement
For power domain adaptation, for CSI(s) reporting, support configuration of more than one power offset values for PDSCH relative to CSI-RS
· FFS: impact on CSI processing requirement
· FFS: details on configuration/indication of the power offset values
· FFS: whether/how to additionally consider the case where CSI-RS power is changed
R1-2303915 FL summary#3 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From April 21st GTW session
Agreement
For CSI feedback with CSI overhead/report payload reduction, further study whether/how to report a common value and/or a differential and/or joint coded value across same CSI quantity of different sub-configurations/adaptation patterns, at least for the following
· CRI
· RI
· PMI
· CQI
· FFS: L1-RSRP
· Other (new) report quantity, if any
Further study whether/how
it is feasible/possible for the UE to skip the evaluations of some sub-configurations/adaptation spatial patterns to reduce the burden at the UE.
R1-2303916 FL summary#4 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From April 25th GTW session
Agreement
For CSI report configuration, if L>1 in a CSI report configuration, at least the following can be included for each sub-configuration for Type 1 SD adaptation
For CSI report configuration for type 2 SD adaptation, further study under which cases sub-configurations may or may not be needed including sub-configuration content.
Agreement
For power domain adaptation, support the following configuration(s) for CSI-RS resource configuration,
R1-2303917 FL summary#5 for spatial and power domain techniques for R18 NES Moderator (Huawei)
From April 26th GTW session
Working Assumption
Al-1-revised and A1-2-revised are supported
· FFS: Which Type of SD adaptation A1-1-revised and A1-2-revised are applicable for
Agreement
For R18 NES, only legacy port configuration values (N1, N2) or (Ng, N1, N2) are supported.
· FFS: Whether/what restriction for A1-1-revised and A-1-2-revised w.r.t number of ports
Decision: As per email decision posted on April 26th,
Agreement
For
Semi-persistent/Aperiodic CSI reporting with , study what
enhancements to the current DCI and MAC-CE mechanisms are needed for gNB
triggering/indication/activation of the N CSI(s) in a reporting instance, where
the N CSI(s) are associated with N sub-configuration(s) from L in a report
config.
Conclusion
From RAN1 perspective, there is no action needed for the LS R1-2302288 from SA5 this time.
Final summary in R1-2304270.
R1-2302334 Cell DTX/DRX for NES FUTUREWEI
R1-2302338 Cell DTX/DRX mechanism for network energy saving Huawei, HiSilicon
R1-2302390 Cell DTX/DRX enhancement for network energy saving Panasonic
R1-2302394 Enhancements on cell DTX/DRX mechanism Nokia, Nokia Shanghai Bell
R1-2302499 Discussions on enhancements on cell DTX/DRX mechanism vivo
R1-2302562 Discussion on enhancements on cell DTX/DRX mechanism OPPO
R1-2302614 Discussion on enhancements on cell DTXDRX mechanism Spreadtrum Communications
R1-2302717 DTX/DRX for network Energy Saving CATT
R1-2302747 Cell DTX/DRX Configuration for Network Energy Saving NEC
R1-2302810 Discussion on enhancements on cell DTX/DRX mechanism Intel Corporation
R1-2302913 Discussion on cell DTX/DRX mechanism Fujitsu
R1-2302945 Discussion on cell DTX/DRX ZTE, Sanechips
R1-2302996 Discussions on cell DTX-DRX for network energy saving xiaomi
R1-2303025 Discussion on enhancements on cell DTX/DRX mechanism InterDigital, Inc.
R1-2303031 Discussion on mechanism of cell DTX/DRX for network energy saving China Telecom
R1-2303057 Network Energy Saving on Cell DTX and DRX Google
R1-2303142 Enhancements on cell DTX/DRX mechanism Samsung
R1-2303203 Enhancements on cell DTX/DRX mechanism ETRI
R1-2303248 Discussion on cell DTX DRX enhancements CMCC
R1-2303310 Discussion on cell DTX/DRX mechanism for network energy saving CEWiT
R1-2303345 On NW energy saving enhancements for cell DTX/DRX mechanism MediaTek Inc.
R1-2303380 Discussion on Enhancement on cell DTX DRX mechanism Transsion Holdings
R1-2303427 Discussion on cell DTX/DRX mechanism LG Electronics
R1-2303497 Discussion on cell DTX/DRX mechanisms Apple
R1-2303532 Enhancements on cell DTX/DRX mechanism Lenovo
R1-2303604 Enhancements on cell DTX and DRX mechanism Qualcomm Incorporated
R1-2303647 Discussion on cell DTX/DRX mechanism Rakuten Mobile, Inc
R1-2303723 Discussion on enhancements on Cell DTX/DRX mechanism NTT DOCOMO, INC.
R1-2303758 RAN1 aspects of cell DTX/DRX Ericsson
R1-2303781 Discussion on potential enhancements on cell DTX/DRX mechanism for NR ITRI
R1-2303815 RAN1 Considerations for Cell DTX and DRX Fraunhofer IIS, Fraunhofer HHI
R1-2303895 Summary of issues for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
[112bis-e-R18-NES-02] – Daewon (Intel)
Email discussion on cell DTX/DRX mechanism by April 26th
- Check points: April 21, April 26
R1-2303896 Discussion summary #1 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in April 17th GTW session
R1-2304014 Discussion summary #2 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From April 19th GTW session
Agreement
From RAN1 point of view, Rel-18 UE supporting cell DTX does not expect to receive and/or process the following signals/channels from the gNB, during non-active periods of cell DTX. The list of signals/channels may be updated based on RAN2/RAN4 input and other signals/channels are not precluded from further discussions.
R1-2304015 Discussion summary #3 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From April 21st GTW session
Agreement
Study L1 signalling for enhancing cell DTX/DRX including activation/deactivation for a single configuration which will have the following characteristics:
Agreement
From RAN1 point of view, Rel-18 UE supporting cell DRX is not expected to transmit the following signals/channels to the gNB during non-active periods of cell DRX. The list of signals/channels may be updated based on RAN2/RAN4 input and other signals/channels are not precluded from further discussions.
· Periodic/Semi-persistent CSI report
· Periodic/Semi-persistent SRS
o FFS: SRS for positioning
· FFS:
o HARQ feedback for SPS PDSCH
· FFS whether there will be exception case(s) for UE transmitting listed signals/channels during non-active periods of DRX
· FFS Whether the listed signals/channels can be configurable by gNB
· FFS: Whether the same or different UE behavior is applicable with or without C-DRX
· FFS: RAN1 to consider impact on system if the channels/signals are not transmitted during non-active period
R1-2304119 Discussion summary #4 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From April 25th GTW session
Further study the following in RAN1:
· Handling of HARQ-ACK codebook generation when configured with cell DTX/DRX
· Handling of PUCCH deferral operation during non-active periods of cell DRX
· Handling of overlapping channels where a least a channel overlaps with non-active periods of cell DTX/DRX
· Handling of signals/channels that can be received/transmitted repeatedly during non-active periods of cell DTX/DRX
· Handling of PUCCH switching during non-active period to an active cell
· Other enhancements are not precluded.
R1-2304120 Discussion summary #5 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From April 26th GTW session
Agreement
For PDDCH monitoring, further work on Rel-18 NES in RAN1 is to follow the RAN2 agreement below:
10. The understanding for the gNB scheduling behaviour for new transmissions during Cell DTX non-active period is that the gNB does not schedule UE-specific dynamic grants/assignments, even if the UE is in C-DRX Active Time. UE doesn’t monitor PDCCH for dynamic grants/assignments for new transmissions during Cell DTX non-active period, even if the UE is in C-DRX Active time. FFS how to deal with any exceptions (e.g. SR if agreed and RACH).
Working Assumption
Support of L1 signaling at least for activation/deactivation of a cell DTX and/or DRX configuration is feasible (e.g., in terms of enabling/disenabling the feature) from RAN1 perspective.
Final summary in R1-2304239.
Please refer to RP-230566 for detailed scope of the WI.
[113-R18-NES] – Yi (Huawei)
Email discussion on NR network energy savings
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2306262 Sorted RAN1 agreements for Rel-18 network energy savings post 113 Rapporteur (Huawei)
R1-2304357 Spatial and Power Adaptations for Network Energy Savings FUTUREWEI
R1-2304406 Techniques in spatial and power domains Nokia, Nokia Shanghai Bell
R1-2304492 Discussions on NES techniques in spatial and power domain vivo
R1-2306011 Discussion on NES techniques in spatial and power domains ZTE, Sanechips (rev of R1-2304527)
R1-2304570 Discussion on NES techniques in spatial and power domains Spreadtrum Communications
R1-2304644 CSI enhancements for network energy saving Huawei, HiSilicon
R1-2304743 Network Energy Saving techniques in spatial and power domain CATT
R1-2304772 Discussion on NW energy saving techniques in spatial and power domains Fujitsu
R1-2304810 Discussion on NWES techniques in spatial and power domain Intel Corporation
R1-2304848 Network Energy Saving in Spatial and Power Domain Google
R1-2304861 Discussion on the spatial and power techniques for NES China Telecom
R1-2304913 Discussion on techniques in spatial and power domains xiaomi
R1-2304946 Network energy savings techniques in spatial domain AT&T
R1-2305071 Discussion on network energy saving techniques in spatial and power domains NEC
R1-2305106 Discussion on spatial and power domains enhancements for network energy saving CMCC
R1-2305143 Discussion on NES techniques in spatial and power domains LG Electronics
R1-2305176 Discussion on techniques in spatial and power domains InterDigital, Inc.
R1-2305209 Network energy saving techniques in spatial and power domains Lenovo
R1-2305255 Discussion on spatial and power domain enhancements to support network energy saving Apple
R1-2305349 Techniques in spatial and power domains Qualcomm Incorporated
R1-2305432 Discussion on techniques in spatial and power domains OPPO
R1-2305526 Techniques in spatial and power domains Samsung
R1-2305551 Discussion on spatial/power domain adaptation ASUSTeK
R1-2305552 On network energy saving techniques in spatial and power domains KT Corp.
R1-2305573 NW energy saving techniques in spatial and power domains Ericsson
R1-2305608 Discussion on spatial and power domain enhancements for NW energy savings NTT DOCOMO, INC.
R1-2305676 On NW energy saving techniques in spatial and power domains MediaTek Inc.
R1-2305710 Discussion of NES techniques in spatial domain and power domain Transsion Holdings
R1-2305765 Spatial and power domain adaptation for network energy saving Panasonic
R1-2305773 Discussion on techniques in spatial and power domains ITRI
R1-2305780 Discussion on NES for signaling of spatial adaptation FGI
R1-2305798 Discussion on NES techniques in spatial and power domains ETRI
R1-2305867 Spatial Domain Adaptation for NES Fraunhofer IIS, Fraunhofer HHI
R1-2305904 Discussion on spatial and power adaptations for network energy savings CEWiT
R1-2306030 FL summary#1 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Monday session
Agreement
Confirm the working assumption with the following update (in blue)
Agreement
For a CSI report configuration with L>1, for Type 1 SD, at least when A1-2-revised is used for the associated codebook configuration,
Agreement (further revised on Wednesday as shown below)
For N>=1 CSI reporting corresponding to N out of L sub-configurations in one reportConfig where each sub-configuration corresponding to an SD adaptation pattern or/[and] a powerControlOffset value,
Note: UE complexity reduction is not precluded.
R1-2306031 FL summary#2 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Tuesday session
Agreement
· For A1-1-revised for Type 2, one or more CSI-RS resources from a CSI-RS resource set for channel measurement can be associated with the same sub-configuration provided in a CSI report configuration
o Resources in the resource set for channel measurement have the same number of antenna ports
· For A1-2-revised for Type 1, all CSI-RS resource(s) (which can be one or more) in the CSI-RS resource set for channel measurement are associated with each sub-configuration provided in a CSI report configuration
o i.e. each CSI-RS resource is associated with all the sub-configurations
o Resources in the resource set for channel measurement have the same number of antenna ports
· FFS: restriction on total number of CSI-RS resources for channel measurement in a CSI-ReportConfig and/or sub-configuration.
R1-2306032 FL summary#3 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Wednesday session
Agreement
For N>=1 CSI reporting corresponding to N out of L sub-configurations in one reportConfig where each sub-configuration corresponding to an SD adaptation pattern or/[and] a powerControlOffset value,
Note: UE complexity reduction is not precluded
Agreement
For Type 1 adaptation, for each sub-configuration,
Agreement
For both spatial domain NES, when UE reports CSIs corresponding to one or more sub-configurations provided in a CSI report configuration,
Agreement
For spatial domain adaptation or power domain adaptation, for CSIs reporting corresponding to N indicated sub-configurations from L sub-configurations in a CSI report, for the case without CSI payload reduction
, where 
is the total number of
CSI-RS resources corresponding to i-th sub-configuration in the CSI-RS
resource set for channel measurement.
R1-2306033 FL summary#4 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Thursday session
Agreement
For Type 1 adaptation, for each sub-configuration, for multi-panel case,
Agreement
For the sub-configuration(s) in a CSI report configuration with L>1,
Above is agreed in addition to what was agreed in previous RAN1 agreements
Agreement
Joint operation of SD and PD adaptation is supported.
Agreement
Agreement
Alt 2: For P-CSI reporting from L configured sub-configurations, support:
, where is the total number of
CSI-RS resources corresponding to i-th sub-configuration in the CSI-RS
resource set for channel measurement. (N=L in the equation)
R1-2306034 Final FL summary for SD and PD adaptation for R18 NES Moderator (Huawei)
From AI 5
R1-2304334 LS on Cell DTX/DRX activation/deactivation RAN2, Huawei
R1-2306169 Draft reply LS on cell DTX/DRX activation/deactivation Moderators (Huawei, Intel)
From Wednesday session
Draft LS in R1-2306169 is endorsed in principle with the following revision.
“With respect to questions
asked by RAN2, RAN1 has made the following agreements:”
Further RAN1 agreements can be added in final LS if necessary.
Friday decision: Final LS (including the agreement on the introduction of new DCI format) is approved in R1-2306246.
R1-2304358 Cell DTX/DRX for NES FUTUREWEI
R1-2304407 Enhancements on cell DTX/DRX mechanism Nokia, Nokia Shanghai Bell
R1-2304493 Discussions on enhancements on cell DTX/DRX mechanism vivo
R1-2304528 Discussion on cell DTX/DRX ZTE, Sanechips
R1-2304571 Discussion on enhancements on cell DTXDRX mechanism Spreadtrum Communications
R1-2304645 Cell DTX/DRX mechanism for network energy saving Huawei, HiSilicon
R1-2304744 DTX/DRX for network Energy Saving CATT
R1-2304773 Discussion on cell DTX/DRX mechanism Fujitsu
R1-2304811 Discussion on enhancements on cell DTX/DRX mechanism Intel Corporation
R1-2304849 Network Energy Saving on Cell DTX and DRX Google
R1-2304862 Discussion on the Cell-DTX/DRX China Telecom
R1-2304914 Discussions on cell DTX-DRX for network energy saving xiaomi
R1-2305073 Cell DTX/DRX Configuration for Network Energy Saving NEC
R1-2305107 Discussion on cell DTX DRX enhancements CMCC
R1-2305144 Discussion on cell DTX/DRX mechanism LG Electronics
R1-2305181 Discussion on enhancements on cell DTX/DRX mechanism InterDigital, Inc.
R1-2305210 Enhancements on cell DTX/DRX mechanism Lenovo
R1-2305256 Discussion on cell DTX/DRX enhancements Apple
R1-2305350 Enhancements on cell DTX and DRX mechanism Qualcomm Incorporated
R1-2305433 Discussion on enhancements on cell DTX/DRX mechanism OPPO
R1-2305527 Enhancements on cell DTX/DRX mechanism Samsung
R1-2305553 Discussion on cell DTX/DRX ASUSTeK
R1-2305574 RAN1 aspects of cell DTX/DRX Ericsson
R1-2305609 Discussion on enhancements on Cell DTX/DRX mechanism NTT DOCOMO, INC.
R1-2305677 On NW energy saving enhancements for cell DTX/DRX mechanism MediaTek Inc.
R1-2305711 Discussion on Enhancement on cell DTX DRX mechanism Transsion Holdings
R1-2305766 Cell DTX/DRX enhancement for network energy saving Panasonic
R1-2305774 Discussion on potential enhancements on cell DTX/DRX mechanism for NR ITRI
R1-2305799 Discussion on cell DTX/DRX mechanism ETRI
R1-2305874 Signaling and Reliability for Cell DTX and DRX Fraunhofer IIS, Fraunhofer HHI
R1-2305905 Discussion on cell DTX/DRX mechanism for network energy saving CEWiT
R1-2306006 Summary of issues for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
R1-2306007 Discussion Summary #1 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in Monday session.
R1-2306110 Discussion Summary #2 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Tuesday session
Agreement
RAN1 supports the group common L1 signaling using PDCCH for cell DTX/DRX activation and deactivation without HARQ feedback
· Send an LS to RAN2 to consider the additional support of a MAC CE based indication
· Subject to UE capability
R1-2306111 Discussion Summary #3 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Wednesday session
Agreement
Confirmation of WA from previous meeting with removal of the two sub-bullets.
Working Assumption
Agreement
R1-2306172 Discussion Summary #4 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Friday session
Agreement
For the group common L1 signaling using PDCCH for cell DTX/DRX activation and deactivation
Final summary in R1-2306173.
Please refer to RP-230566 for detailed scope of the WI. Rapporteur to provide initial input on higher layer signalling under agenda item 9.7. For input on higher layer signalling from any other source, please include it as part of your tdoc to relevant sub-agenda items.
[114-R18-NES] – Yi (Huawei)
Email discussion on NR network energy savings
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2306552 Higher layer signalling for Rel-18 NES Huawei, HiSilicon
R1-2308642 Comments collection for RRC parameters for R18 NES Moderator (Huawei)
R1-2308669 Sorted RAN1 agreements for Rel-18 network energy savings post 114 Rapporteur (Huawei)
R1-2306472 Techniques in spatial and power domains Nokia, Nokia Shanghai Bell
R1-2306504 CSI enhancements for network energy saving Huawei, HiSilicon
R1-2306575 Discussions on network energy savings techniques in spatial and power domains Ruijie Network Co. Ltd
R1-2306624 Spatial and Power Adaptations for Network Energy Savings FUTUREWEI
R1-2306657 Discussion on NES techniques in spatial and power domains Spreadtrum Communications
R1-2306762 Discussions on NES techniques in spatial and power domain vivo
R1-2306802 Spatial and power domain adaptation for network energy saving Panasonic
R1-2306828 Discussion on NWES techniques in spatial and power domain Intel Corporation
R1-2306946 Discussion on network energy saving techniques in spatial and power domains NEC
R1-2306963 Network Energy Saving in Spatial and Power Domain Google
R1-2307099 Network Energy Saving techniques in spatial and power domain CATT
R1-2307139 Discussion on NES techniques in spatial and power domains ZTE, Sanechips
R1-2307162 Discussion on NW energy saving techniques in spatial and power domains Fujitsu
R1-2307207 Discussion on spatial and power domains enhancements for network energy saving CMCC
R1-2307290 Discussion on remaining issues for spatial and power domain enhancements to support network energy saving Apple
R1-2307396 "Discussion on techniques in spatial and power domains" xiaomi
R1-2307404 On network energy saving techniques in spatial and power domains KT Corp.
R1-2307483 Discussion on spatial and power domain enhancements for NW energy savings NTT DOCOMO, INC.
R1-2307540 Discussion on techniques in spatial and power domains OPPO
R1-2307623 Discussion on spatial and power domain CSI adaptation for NES China Telecom
R1-2307690 Remaining Issues on NES techniques in spatial and power domains Samsung
R1-2307748 Discussion on NES techniques in spatial and power domains ETRI
R1-2307765 Discussion of NES techniques in spatial domain and power domain Transsion Holdings
R1-2307779 Discussion on TCI state and beam management for NES spatial and power domain adaptation FGI
R1-2307792 Discussion on NES techniques in spatial and power domains LG Electronics
R1-2307813 Network energy saving techniques in spatial and power domains Lenovo
R1-2307821 Discussion on techniques in spatial and power domains InterDigital, Inc.
R1-2307891 Discussion on NES techniques in spatial and power domain ITRI
R1-2307938 Techniques in spatial and power domains Qualcomm Incorporated
R1-2307984 Spatial Domain Adaptation for NES Fraunhofer IIS, Fraunhofer HHI
R1-2307987 NW energy saving techniques in spatial and power domains Ericsson
R1-2308008 Discussion on spatial and power adaptations for network energy savings CEWiT
R1-2308081 On NES Techniques in spatial and power domains MediaTek Inc.
R1-2308105 Discussion on spatial/power domain adaptation ASUSTeK
R1-2308250 FL summary#1 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Monday session
Conclusion
· No further work on BM enhancements for R18 NES.
· No further work on TCI configuration enhancement for R18 NES.
Conclusion
· No further enhancements for PMI reduction in R18 NES.
· No further enhancements for RI reduction in R18 NES.
· No support of UE reporting PDSCH power reduction tolerance in R18 NES.
Agreement
For
SD and/or PD adaptation without UE
complexity reduction, CPU counting of A/SP-CSI reporting is based on 
for
CSIs reporting corresponding to N indicated sub-configurations from L
configured sub-configurations in a CSI report.
Agreement
For sub-configuration triggering of A-CSI, an indication for N sub-configurations out of L sub-configurations for a triggering state is configured in CSI-AssociatedReportConfigInfo.
No change to current CSI request field in DCI.
Conclusion
There is no consensus to support the following
Agreement
R1-2308251 FL summary#2 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Tuesday session
Conclusion
· No simultaneous configuration of Type 1 SD and Type 2 SD adaptation in a same CSI report configuration
Agreement
For power domain adaptation only, all CSI-RS resource(s) (which can be one or more) in the CSI-RS resource set for channel measurement are associated with each sub-configuration provided in a CSI report configuration
Agreement
For joint operation of SD and PD, each subConfig contains corresponding parameters for an SD adaptation and/or parameters for a PD adaptation.
Agreement
For sub-configuration triggering of SP-CSI on PUSCH report, an indication for N sub-configurations out of L sub-configurations for a triggering state is configured in CSI-SemiPersistentOnPUSCH-TriggerState.
· No change to current CSI request field in DCI.
R1-2308252 FL summary#3 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Wednesday session
Agreement
Down-select from the below for priority rule determination for CSI reporting of multiple sub-configurations
Agreement
For N(>1) CSIs reporting with multiple sub-configurations without payload/complexity reduction,
· Each CSI can be a single-part, or two-part CSI, and contains the same types of CSI parameters/quantities as legacy, when applicable/if reported;
· The mapping order of CSI fields of one sub-configuration is as legacy mapping order of CSI fields of one CSI report;
· Part 2 CSI priority reporting level follows wideband CSI first, then even subband CSI and odd subband CSI;
R1-2308253 FL summary#4 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Thursday session
Agreement
For CSIs across multiple sub-configurations in one CSI reportConfig map different sub-configurations based on RAN1#114 agreement in 9.7.1
· For Part 2 priority reporting level
o Option 1: for a given band type from {wideband, even subband, odd subband}, the omission order follows the priority order determined by sub-configuration index
Agreement (modified as shown in red in Friday session)
For a CSI report configuration containing sub-configuration(s), if a CSI-RS resource is referred by M sub-configurations among X sub-configurations, the CSI-RS resource is counted M times and CSI-RS ports within the CSI-RS resource are counted by
· Option
2A: 
for Type 1 SD
adaptation,
and 
for Type 2 SD or PD
adaptation.
is nrofPorts configured in NZP-CSI-RS-Resource and 
is the number of CSI-RS
ports in sub-configuration s derived from port subset indication.
It is understood that further discussions are necessary.
Agreement
For Type 1 SD for multi-panel case,
· Introduce a new mixed codebook combination {Type 1 Single Panel, Type 1 Multi Panel, Null} in R18 for FG codebookComboParameterAddition (indicating the UE supports the mixed codebook combinations in a slot)
· Note: gNB can configure either Type 1 single panel codebook or Type 1 multi-panel codebook for a sub-configuration from one or multiple sub-configurations within one CSI report configuration if a UE reports support of multi-panel operation.
R1-2308599 FL summary#5 for SD and PD adaptation for R18 NES Moderator (Huawei)
Presented in Friday session.
Final summary in R1-2308600.
R1-2306473 Enhancements on cell DTX/DRX mechanism Nokia, Nokia Shanghai Bell
R1-2306505 Cell DTX/DRX mechanism for network energy saving Huawei, HiSilicon
R1-2306577 Discussions on enhancements on cell DTX/DRX mechanism Ruijie Network Co. Ltd
R1-2306625 Cell DTX/DRX for NES FUTUREWEI
R1-2306658 Discussion on enhancements on cell DTXDRX mechanism Spreadtrum Communications
R1-2306763 Discussions on enhancements on cell DTX/DRX mechanism vivo
R1-2306803 Cell DTX/DRX enhancement for network energy saving Panasonic
R1-2306829 Discussion on enhancements on cell DTX/DRX mechanism Intel Corporation
R1-2306948 Cell DTX/DRX Configuration for Network Energy Saving NEC
R1-2306964 Network Energy Saving on Cell DTX and DRX Google
R1-2307100 DTX/DRX for network Energy Saving CATT
R1-2307140 Discussion on cell DTX/DRX ZTE, Sanechips
R1-2307163 Discussion on cell DTX/DRX mechanism Fujitsu
R1-2307208 Discussion on cell DTX/ DRX mechanism CMCC
R1-2307291 Discussion on remaining issues for cell DTX/DRX mechanism Apple
R1-2307397 Discussions on cell DTX-DRX for network energy saving xiaomi
R1-2307484 Discussion on enhancements on Cell DTX/DRX mechanism NTT DOCOMO, INC.
R1-2307541 Discussion on enhancements on cell DTX/DRX mechanism OPPO
R1-2307624 Discussion on the mechanism of Cell DTX/DRX for NES China Telecom
R1-2307691 Remaining issues on cell DTX/DRX mechanism Samsung
R1-2307749 Discussion on cell DTX/DRX mechanism ETRI
R1-2307766 Discussion on Enhancement on cell DTX DRX mechanism Transsion Holdings
R1-2307793 Discussion on cell DTX/DRX mechanism LG Electronics
R1-2307814 Enhancements on cell DTX/DRX mechanism Lenovo
R1-2307822 Discussion on enhancements on cell DTX/DRX mechanism InterDigital, Inc.
R1-2307838 Considerations of Cell DTX/DRX Signaling and Reliability Fraunhofer IIS, Fraunhofer HHI
R1-2307939 Enhancements on cell DTX and DRX mechanism Qualcomm Incorporated
R1-2307988 RAN1 aspects of cell DTX/DRX Ericsson
R1-2308009 Discussion on cell DTX/DRX mechanism for network energy saving CEWiT
R1-2308082 On enhancements of cell DTX/DRX mechanism MediaTek Inc.
R1-2308106 Discussion on cell DTX/DRX ASUSTeK
R1-2308350 Summary of issues for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Monday session
Agreement
DCI format 2_X, for activation and deactivation of cell DTX and DRX configuration,
Above applies at least for sTRP case.
Working Assumption (to be confirmed on Wed). Confirmed in Friday session as Agreement
For at least the case where one cell DTX/DRX pattern is configured, an information block field of DCI format 2_X for activation and deactivation of cell DTX and DRX configuration supports the following:
Above does not imply that multiple DTX/DRX patterns is not supported.
Agreement
Support new RNTI (e.g. nes-RNTI) which is configured by higher layer, for scrambling of DCI format 2_X.
R1-2308351 Discussion summary #1 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Tuesday session
Agreement
From RAN1 point of view, DCI format 2_X supports activation/deactivation of cell DTX/DRX configuration of multiple serving cells and support activation/deactivation per cell.
· UE monitor DCI format 2_X in one serving cell.
Agreement
Delay that is applied after DCI Format 2_X reception that activate/deactivate cell DTX/DRX configuration is introduced in Rel-18.
Agreement
DCI format 2_X is monitored in the common search space.
Note: Search space set configuration for DCI format 2_X is separately provided by higher layers.
Agreement
The following high layer signaling are to be included to the RRC parameter list for new DCI format 2_X for activation and deactivation of cell DTX/DRX
R1-2308352 Discussion summary #2 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Wednesday session
Agreement
Agreement
For each serving cell configured with L1 signaling based activation/deactivation of cell DTX and/or cell DRX configuration, starting bit position of an information block of DCI format 2_X is provided by UE specific higher layer signaling.
|
SCS of PDCCH (kHz) |
Value of D (in unit of slot) |
|
15 |
3 |
|
30 |
6 |
|
60 |
12 |
|
120 |
24 |
|
480 |
96 |
|
960 |
192 |
Agreement
Rel-18 UE supporting cell DTX is not required to monitor the following signals/channels from the gNB, during non-active periods of cell DTX
Conclusion:
· HARQ-ACK of SPS PDSCH transmitted is not impacted by non-active period of cell DRX.
·
Note: HARQ-ACK of SPS PDSCH not
received due to non-active period of cell DTX is impacted.
R1-2308496 Discussion summary #3 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in Thursday session.
R1-2308497 Discussion summary #4 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From friday session
Agreement
For the FFS from agreement from RAN1 #112bis
· SRS for positioning is not impacted by cell DRX operation.
Conclusion
Final summary in R1-2308620.
[114bis-R18-NES] – Yi (Huawei)
Email discussion on NR network energy savings
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2310576 RRC parameter list for Rel-18 network energy savings post 114bis Moderator (Huawei)
R1-2308893 Maintenance of CSI enhancements for NES Huawei, HiSilicon
R1-2308948 Techniques in spatial and power domains Nokia, Nokia Shanghai Bell
R1-2308990 Remaining issues on techniques in spatial and power domains Spreadtrum Communications
R1-2309079 Remaining issues on NES techniques in spatial and power domain vivo
R1-2309178 Discussion on NES techniques in spatial and power domains ZTE, Sanechips
R1-2309192 Maintenance issues of enhancements on NES spatial and power domain operations Intel Corporation
R1-2309261 Network Energy Saving in Spatial and Power Domain Google
R1-2309290 Remaining issues on techniques in spatial and power domains CEWiT
R1-2309294 Remaining issues on network energy saving techniques in spatial and power domains NEC
R1-2309302 Remaining issues of NES techniques in spatial and power domains LG Electronics
R1-2309311 Discussion on Remaining issues of NES FUTUREWEI
R1-2309380 Remaining issues on NES techniques in spatial and power domains Samsung
R1-2309461 Remaining issues on NES techniques in spatial and power domains xiaomi
R1-2309531 Network Energy Saving techniques in spatial and power domain CATT
R1-2309552 Remaining issues on SD and PD NES techniques China Telecom
R1-2309596 Discussion on remaining issue for techniques in spatial and power domains OPPO
R1-2309647 Remaining details on NW energy saving techniques in spatial and power domains Fujitsu
R1-2309676 Remaining issues on spatial and power domains enhancements for network energy saving CMCC
R1-2309720 Remaining issues of NES techniques in spatial and power domains Transsion Holdings
R1-2309838 On remaining issues for spatial and power domain enhancements to support network energy saving Apple
R1-2309894 Correction on spatial adaptation ASUSTeK
R1-2309940 Remaining issues on NES techniques in spatial and power domains InterDigital, Inc.
R1-2309942 Spatial and power domain adaptation for network energy saving Panasonic
R1-2309949 Maintenance on Network energy saving techniques in spatial and power domains Lenovo
R1-2310007 Maintenance on NES techniques in spatial and power domains MediaTek Inc.
R1-2310038 Maintenance of spatial and power domain enhancements for NW energy savings NTT DOCOMO, INC.
R1-2310094 Maintenance of NW energy saving techniques in spatial and power domains Ericsson
R1-2310146 Remaining aspects of spatial and power domain adaptation Qualcomm Incorporated
R1-2310307 FL summary#1 for SD and PD adaptation for R18 NES Moderator (Huawei)
Presented in Monday session.
R1-2310308 FL summary#2 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Tuesday session
Agreement
Support gNB can configure report quantities of 'cri-RI-i1-CQI', 'cri-RI-CQI', or 'cri-RI-i1'.
Agreement
For CSI mapping of subbands for a CSI report having multiple sub-configurations, odd sub-band CSI(s) of all sub-configurations in one multi-CSI reporting are mapped after all even sub-band CSI(s) in one multi-CSI reporting.
Conclusion
No consensus to have spec update with respect to the issue 6 in R1-2310308.
Agreement
·
For a CSI report config
containing sub-configuration(s), support 
in Table 5.4-2 of TS 38.214 for CSI computation delay requirements.
· For CPU occupation and update, if there are not enough CPUs for processing the entire CSI report, legacy UE behavior is used
Comeback support of Z1, Z1’. If no consensus, only Z2, Z2’ will be supported.
Friday confirmation: Only Z2, Z2’ will be supported.
Agreement
For a CSI report having sub-configuration including port subset indication, CSI-RS port re-indexing is supported.
Agreement
For CSI reporting in PUCCH, Table 6.3.1.1.2-7, Table 6.3.1.1.2-9 and Table 6.3.1.1.2-10 in TS38.212 are applicable for NES
For CSI reporting on PUSCH, Table 6.3.2.1.2-3 and Table 6.3.2.1.2-4 in TS38.212 are applicable for NES
Further discuss in this meeting about the applicability of below for NES
· Table 6.3.1.1.2-8/8A/11 in TS38.212 (or a new table for replacement of Table 6.3.1.1.2-11)
· Table 6.3.2.1.2-5 in TS38.212 (or a new table for replacement)
Agreement
Remove the square brackets as below for TS 38.214
|
5.2.2.5 CSI reference resource definition <omitted text> - if a
sub-configuration indicates a power offset [powerOffset], for CQI
calculation, the UE shall assume the corresponding PDSCH signals transmitted
on the antenna ports of a CSI-RS resource would have a ratio of EPRE to
CSI-RS EPRE equal to the <omitted text> |
· The range of [powerOffset] in the above TP is [0…23] in dB with step size of 1 dB.
R1-2310309 FL summary#3 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Wednesday session
Agreement
· Adopt the following TP for TS 38.214, Clause 5.2.1.1
=== start of TP===
The time domain behavior of the CSI-ReportConfig is indicated by the higher layer parameter reportConfigType and can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For 'periodic' and 'semiPersistentOnPUCCH'/'semiPersistentOnPUSCH' CSI reporting, the configured periodicity and slot offset applies in the numerology of the UL BWP in which the CSI report is configured to be transmitted on. The higher layer parameter reportQuantity indicates the CSI-related, L1-RSRP-related, L1-SINR-related, CapabilityIndex-related or TDCP-related quantities to report. The reportFreqConfiguration indicates the reporting granularity in the frequency domain, including the CSI reporting band and if PMI/CQI reporting is wideband or sub-band. The timeRestrictionForChannelMeasurements parameter in CSI-ReportConfig can be configured to enable time domain restriction for channel measurements and timeRestrictionForInterferenceMeasurements can be configured to enable time domain restriction for interference measurements. The CSI-ReportConfig can also contain CodebookConfig, which contains configuration parameters for Type-I, Type II, Enhanced Type II CSI, Further Enhanced Type II Port Selection, Enhanced Type II for coherent joint transmission (CJT), Further Enhanced Type II Port Selection for CJT, Enhanced Type II for predicted PMI, or Further Enhanced Type II Port Selection for predicted PMI including codebook subset restriction when applicable, and configurations of group-based reporting. A UE is not expected to be configured with a CSI report setting associated with a dormant DL BWP if the reportConfigType is set to 'aperiodic'. A CSI-ReportConfig can contain a list of sub-configurations, provided by the higher layer parameter [csi-ReportSubConfigList], where each sub-configuration is identified by [csi-ReportSubConfigID] and corresponds to a list of one or more CSI-RS resources or corresponds to a CSI-RS antenna port subset, and/or corresponds to a power offset for PDSCH relative to CSI-RS additional to powerControlOffset of the CSI-RS resource. A UE is not expected to be configured with a CSI-ReportConfig that contains a mix of sub-configuration(s) each corresponding to a list of one or more CSI-RS resources and some other sub-configuration(s) each corresponding to CSI-RS antenna port subset.
=== end of TP===
Conclusion
There is no consensus to support the following:
· A UE only reports PMI in CSI part 2 for the first sub-configuration among the sub-configurations with the same RI reported across sub-configurations.
Agreement
From RAN1 perspective, up to 4 CSI report configurations can be configured in a BWP for SP CSI reporting on PUCCH where one or more report configurations can contain a list of sub-configuration(s).
· Send an LS to RAN2 including the relevant agreements made in UE feature discussions.
Comeback on the LS
R1-2310577 SP-CSI reporting for network energy savings Huawei
Thursday decision: The draft LS is endorsed. Final LS is approved in R1-2310578.
Agreement
Only codebook type 1 for PMI is supported for type 2 SD adaptation and PD adaptation.
Conclusion
There is no consensus on the following proposal:
For a P/SP-CSI report configuration containing a list of L sub-configurations, if at least one subConfig (which is the triggered one for SP-CSI reporting, or configured one for P-CSI report) is associated with more than one CSI-RS resource, nCSI_ref is the smallest value >=5*2μDL; otherwise, it is the smallest value no smaller than 4*2μDL.
R1-2310310 FL summary#4 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Thursday session
For RAN1#115:
Further discuss in the next meeting for the following case:
A UE configured with CSI report configuration with e.g. two sub-configurations (sub-config#1 and sub-config#2), each with e.g. two CSI-RS resources, none of the CSI-RS Tx occasions of sub-config#1 meet the CSI reference resource, i.e. they are later than CSI ref. resource, the UE shall
· Alt 1: report the CSI report, according to current spec
· Alt 2: report the CSI sub-report#2 only and drop the CSI sub-report#1 only
· Alt 3: drop the entire CSI report
R1-2310574 FL summary#5 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Friday session
For RAN1#115
· Further check whether there is any issue according to the current specification that, for the CSI mapping of a CSI report configuration having L sub-configurations, Part 2 wideband CSIs have the same priority and are dropped per sub-configuration level in the ascending order of sub-configuration index.
· Further check whether part 1 CSI can already be dropped in legacy for a CSI report configuration, and if so, then Part 1 CSIs are dropped per sub-configuration level, in the ascending order of sub-configuration index.
· Companies are encouraged to provide TPs for necessary changes.
Agreement
For CSI reporting on PUCCH and PUSCH, at least one new table is introduced for the scenarios of Table 6.3.1.1.2-11 and Table 6.3.2.1.2-5 in TS38.212, with update corresponding to the CSI mapping order of part 2 CSI even/odd subbands for CSI reporting corresponding to one or more sub-configurations.
Agreement
· Adopt the following TP for TS 38.214 for the above agreements
5.2.1.4.2 Report Quantity Configurations
---------------------------------------------------- Unchanged text is omitted ---------------------------------------------------------
If the UE is configured with a CSI-ReportConfig that contains a list of sub-configurations, provided by the higher layer parameter [csi-ReportSubConfigList]:
−
tThe UE expects
to be configured with the higher layer parameter codebookType set to
'typeI-SinglePanel' or 'typeI-MultiPanel'. If the UE indicates a capability for
supporting mixed codebook combination in a slot with [ABC], each
sub-configuration can be configured with the higher layer parameter codebookType
set to 'typeI-SinglePanel' or 'typeI-MultiPanel'.
−
- Each
sub-configuration can be configured with an antenna port subset using the
higher layer bitmap parameter [port-subsetIndicator] which contains the
bit sequence 
, where 
is the MSB
and 
is the LSB,
bit 
corresponds
to antenna port 
, and 
is the
number of ports nrofPorts configured for the CSI-RS resources(s) within
the NZP-CSI-RS-ResourceSet contained in the CSI-ResourceConfig
for channel measurement that corresponds to the CSI-ReportConfig. A bit
value 0 in [port-subsetIndicator] indicates that the corresponding
antenna port is disabled for the sub-configuration, whereas bit value 1
indicates that the antenna port is enabled and belongs to the antenna port
subset for the sub-configuration. For the derivation of PMI,
antenna ports corresponding to all bits with value of 1 in
[port-subsetIndicator] are mapped to
consecutive antenna ports starting at CSI-RS antenna
port 3000 in increasing order of the bit position in [port-subsetIndicator].
---------------------------------------------------- Unchanged text is omitted -------------------------------------------------------
Agreement
------------------------------ Text Proposal (TP#1) for 38.212, Sections 6.3.1.1.2 and 6.3.2.1.2 --------------------------
*** Unchanged text omitted ***
If
none of the CSI reports for transmission on a PUCCH is of two parts, the CSI
fields of all CSI reports, in the order from upper part to lower part in Table
6.3.1.1.2-12, are mapped to the UCI bit sequence 
starting
with 
. The most
significant bit of each field is mapped to the lowest order information bit for
that field, e.g. the most significant bit of the first field is mapped to.
Table 6.3.1.1.2-12: Mapping
order of CSI reports to UCI bit sequence 
, without
two-part CSI report(s)
|
UCI bit sequence |
CSI report number |
|
|
CSI report #1 as in Table 6.3.1.1.2-7/7A/8/8B |
|
CSI report #2 as in Table 6.3.1.1.2-7/7A/8/8B |
|
|
… |
|
|
CSI report #n as in Table 6.3.1.1.2-7/7A/8/8B |
|
|
Note:
For a CSI report #i containing Ni CSI sub-reports, where |
|
If
at least one of the CSI reports for transmission on a PUCCH is of two parts,
two UCI bit sequences are generated, 
and 
. The CSI
fields of all CSI reports, in the order from upper part to lower part in Table
6.3.1.1.2-13, are mapped to the UCI bit sequence starting
with 
. The most
significant bit of each field is mapped to the lowest order information bit for
that field, e.g. the most significant bit of the first field is mapped to. The CSI
fields of all CSI reports, in the order from upper part to lower part in Table
6.3.1.1.2-14, are mapped to the UCI bit sequence starting
with 
. The most
significant bit of each field is mapped to the lowest order information bit for
that field, e.g. the most significant bit of the first field is mapped to 
. If the length
of UCI bit sequence 
is less than
3 bits, zeros shall be appended to the UCI bit sequence until its length equals
3.
Table 6.3.1.1.2-13: Mapping
order of CSI reports to UCI bit sequence ,
with two-part CSI report(s)
|
UCI bit sequence |
CSI report number |
|
|
CSI report #1 if CSI report #1 is not of two parts, or CSI report #1, CSI part 1, if CSI report #1 is of two parts, as in Table 6.3.1.1.2-7/7A/8/8B/9/9A/9B |
|
CSI report #2 if CSI report #2 is not of two parts, or CSI report #2, CSI part 1, if CSI report #2 is of two parts, as in Table 6.3.1.1.2-7/7A/8/8B/9/9A/9B |
|
|
… |
|
|
CSI report #n if CSI report #n is not of two parts, or CSI report #n, CSI part 1, if CSI report #n is of two parts, as in Table 6.3.1.1.2-7/7A/8/8B/9/9A/9B |
|
|
Note: For a CSI report
#i containing Ni CSI sub-reports, where |
|
where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.1.1.2-13 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].
Table 6.3.1.1.2-14: Mapping
order of CSI reports to UCI bit sequence ,
with two-part CSI report(s)
|
UCI bit sequence |
CSI report number |
|
|
CSI
report #1, CSI part 2 wideband, as in Table 6.3.1.1.2-10/10A/10B |
|
CSI
report #2, CSI part 2 wideband, as in Table 6.3.1.1.2-10/10A/10B |
|
|
… |
|
|
CSI
report #n, CSI part 2 wideband, as in Table 6.3.1.1.2-10/10A/10B |
|
|
CSI
report #1, CSI part 2 subband, as in Table 6.3.1.1.2-11/11A/11B/[New Table] |
|
|
CSI
report #2, CSI part 2 subband, as in Table 6.3.1.1.2-11/11A/11B/[New Table] |
|
|
… |
|
|
CSI
report #n, CSI part 2 subband, as in Table 6.3.1.1.2-11/11A/11B/[New Table] |
|
|
Note: For a CSI report
#i containing Ni CSI sub-reports, where -
-
CSI sub-report #1, CSI sub-report #2, …, CSI
sub-report # |
|
where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.1.1.2-14 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].
*** Unchanged text omitted ***
Table 6.3.2.1.2-6: Mapping
order of CSI reports to UCI bit sequence 
,
with two-part CSI report(s)
|
UCI bit sequence |
CSI report number |
|
|
CSI part 1 of CSI report #1 as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B |
|
CSI part 1 of CSI report #2 as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B |
|
|
… |
|
|
CSI part 1 of CSI report #n as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B |
|
|
Note: For a CSI report
#i containing Ni CSI sub-reports, where |
|
where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.2.1.2-6 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].
Table 6.3.2.1.2-7: Mapping
order of CSI reports to UCI bit sequence 
,
with two-part CSI report(s)
|
UCI bit sequence |
CSI report number |
|
|
CSI report #1, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B, or
CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B, |
|
CSI report #2, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B, or
CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B, |
|
|
… |
|
|
CSI report #n, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B, or
CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B, |
|
|
CSI report #1, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D/[New Table], or
CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B, |
|
|
CSI report #2, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D/[New Table], or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B, if CSI part 2 exists for CSI report #2 |
|
|
… |
|
|
CSI report #n, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D/[New Table], or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B, if CSI part 2 exists for CSI report #n |
|
|
Note: For a CSI report
#i containing Ni CSI sub-reports, where -
CSI part 2 wideband of all CSI sub-reports
are mapped to the corresponding -
CSI sub-report #1, CSI sub-report #2, …, CSI
sub-report #
|
|
where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.2.1.2-7 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].
*** Unchanged text omitted ***
---------------------------------------------------------- End Text Proposal --------------------------------------------------------
Agreement
· Adopt the following TP for TS 38.213.
---------------------------------Start of Text Proposal on TS 38.213 v18.0.0------------------
9.2.5 UE procedure for reporting multiple UCI types
< Unchanged parts are omitted >
If a UE would multiplex CSI reports that include Part 2 CSI reports in a PUCCH resource, the UE determines the PUCCH resource and a number of PRBs for the PUCCH resource or a number of Part 2 CSI reports assuming that each of the CSI reports indicates rank 1, or rank combination of {1, 1}, or rank 1 per CSI sub-report, if applicable. If the higher layer parameter csi-ReportMode of CSI reports is set to 'Mode2', the UE determines the PUCCH resource and a number of PRBs for the PUCCH resource or a number of Part 2 CSI reports assuming that each CRI in the CSI report is associated with a resource pair.
< Unchanged parts are omitted >
---------------------------------End of Text Proposal on TS 38.213 v18.0.0--------------------
For RAN1#115:
For Type 2 SD adaptation or joint operation of Type 2 SD and PD adaptation, whether the list of NZP CSI-RS resources configured for a sub-configuration is identical to or has no intersection with the list of NZP CSI-RS resources configured for the other sub-configuration(s) within the same CSI-ReportConfig.
· Companies are encouraged to check the example as provided in section 2.5 in R1- 2309647
For Type 1 SD adaptation, or joint operation of Type 1 SD and PD adaptation,
· ‘typeI-SinglePanel-codebookSubsetRestriction-i2’ is configured for each sub-configuration
· if a UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-CQI', the UE expects to be configured with higher layer parameter non-PMI-PortIndication in each sub-configuration
· if all the sub-configurations are configured with port antenna subset indication, the codebook subset restriction, ri restriction, N1 and N2 (and Ng when applicable) should be configured separately in each sub-configuration, instead of being configured in CodebookConfig in the CSI report configuration; otherwise, the CodebookConfig should be configured as legacy in the CSI report configuration.
Agreement
Report quantities of 'cri-RSRP', 'cri-SINR', or 'cri-SINR- Index ' are NOT applicable to NES.
For RAN1#115 (Companies are encouraged to study and be ready to make decision in the next meeting)
For a CSI report configuration containing sub-configuration(s), if a CSI-RS resource is referred by M sub-configurations among X sub-configurations, the CSI-RS resource is counted M times and CSI-RS ports within the CSI-RS resource are counted by agreed in previous meeting, and
R1-2310575 Final FL summary for SD and PD adaptation for R18 NES Moderator (Huawei)
R1-2308894 Maintenance of Cell DTX/DRX for NES Huawei, HiSilicon
R1-2308949 Enhancements on cell DTX/DRX mechanism Nokia, Nokia Shanghai Bell
R1-2308991 Remaining issues on enhancements on cell DTX/DRX mechanism Spreadtrum Communications
R1-2309080 Remaining issues on enhancements on cell DTX/DRX mechanism vivo
R1-2309179 Discussion on cell DTX/DRX ZTE, Sanechips
R1-2309262 Network Energy Saving on Cell DTX and DRX Google
R1-2309291 Enhancements on cell DTX/DRX mechanism CEWiT
R1-2309296 Remaining issues on cell DTX/DRX configuration for Network Energy Saving NEC
R1-2309303 Remaining issues of cell DTX/DRX mechanism LG Electronics
R1-2309312 DCI 2_9 for Cell DTX/DTX FUTUREWEI
R1-2309381 Remaining issues on cell DTX/DRX mechanism Samsung
R1-2309462 Discussions on cell DTX-DRX for network energy saving xiaomi
R1-2309532 DTX/DRX for network Energy Saving CATT
R1-2309553 Remaining issues on cell DTX/DRX mechanism China Telecom
R1-2309597 Discussion on remaining issue for enhancements on cell DTX/DRX mechanism OPPO
R1-2309648 Remaining details on cell DTX/DRX mechanism Fujitsu
R1-2309677 Remaining issues on cell DTX/DRX mechanism CMCC
R1-2309705 Remaining issues on cell DTX/DRX mechanism ETRI
R1-2309721 Remaining issues on enhancement on cell DTXDRX mechanism Transsion Holdings
R1-2309839 On remaining issues for cell DTX/DRX mechanism Apple
R1-2309893 Correction on cell DTX ASUSTeK
R1-2309941 Remaining issues on cell DTX/DRX mechanism InterDigital, Inc.
R1-2309943 Cell DTX/DRX enhancement for network energy saving Panasonic
R1-2309950 Maintenance on enhancements on cell DTX/DRX mechanism Lenovo
R1-2310008 Maintenance on cell DTX/DRX mechanism MediaTek Inc.
R1-2310039 Maintenance of enhancements on Cell DTX/DRX mechanism NTT DOCOMO, INC.
R1-2310095 Maintenance for cell DTX/DRX Ericsson
R1-2310147 Remaining aspects of cell DTX and DRX Qualcomm Incorporated
R1-2310243 Issues on Cell DTX/DRX Fraunhofer IIS, Fraunhofer HHI
R1-2310336 Summary of maintenance issues for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
R1-2310337 Discussion summary #1 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in Monday session.
R1-2310338 Discussion summary #2 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Tuesday session
Agreement
Send LS to RAN2 to ask to consider the following RAN1 agreements and ask RAN2 to capture them in RAN2 specification appropriately.
§ PDCCHs associated with DCI format 2_0 – DCI Format 2_5
o HARQ-ACK of SPS PDSCH transmitted is not impacted by non-active period of cell DRX.
o The following channels are not impacted by non-active period of cell DRX
§ HARQ-ACK of a DCI format without scheduling a PDSCH
Include a note saying that for the conclusions, RAN1 does not expect any specification impact.
Comeback on LS.
R1-2310475 Draft LS on cell DTX/DRX operations Moderator (Intel Corporation)
Wednesday decision: The draft LS is endorsed. Final LS is approved in R1-2310476.
Agreement
· The following TP is endorsed for TS38.212.
|
Reason for change: The current wording doesn’t clearly capture the cases where both cell DTX and cell DRX are configured or only cell DTX or cell DTX is configured . |
||||||||||||||||||||||||||||||||||||||||||
|
Summary of change: Replace “Activating or de-activating the cell DTX/DRX configuration of one or multiple serving cells for one or more UEs.” by “Activating or de-activating the cell DTX and/or DRX configuration of one or multiple serving cells for one or more UEs.” |
||||||||||||||||||||||||||||||||||||||||||
|
Consequences if not approved: unclear specification |
||||||||||||||||||||||||||||||||||||||||||
|
*** Unchanged parts are omitted *** Table 7.3.1-1: DCI formats
*** Unchanged parts are omitted *** |
Possible alternatives related to DCI format 2-9 during non-active periods of C-DRX
R1-2310452 Discussion summary #3 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in Wednesday session.
R1-2310453 Discussion summary #4 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Thursday session
Agreement
For CSI report associated with P/SP CSI-RS resource and configured with reportQuantity including RI, when cell DTX is configured
Agreement
Cell DTX/DRX operation is only supported for sTRP.
Agreement
TP #22-4 (old #16-1) to TS38.214 - with updated "reasons for change" as shown as per Friday session
|
Reasons for change: For a CSI reporting configured with reportQuantity comprising at least ‘RI’, if the time domain restriction for channel measurements or interference measurements is enabled and the most recent CSI-RS associated with the CSI resource setting occurs during non-active periods of cell DTX, UE has to skip this CSI reporting, which may impact the system performance. |
|
Summary of change: When cell DTX operation is configured and the time domain restriction for channel measurements or interference measurements is enabled, the CSI-RS used for the corresponding measurements can be redefined as the most recent CSI-RS within the active periods of cell DTX. |
|
Consequences if not approved: For a CSI reporting, if the time domain restriction for channel measurements or interference measurements is enabled and the most recent CSI-RS associated with the CSI resource setting occurs during non-active periods of cell DTX, UE has to skip this CSI reporting, which may impact the system performance. |
|
---------------------------- Start of Text Proposal for TS 38.214 ----------------------------- 5.2.2.1 Channel quality indicator (CQI) < Unchanged parts are omitted > If the higher layer parameter timeRestrictionForChannelMeasurements is set to "notConfigured", the UE shall derive the channel measurements for computing CSI value reported in uplink slot n based on only the NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting. If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing CSI reported in uplink slot n based on only the most recent, no later than the CSI reference resource, in cell DTX active time if cell DTX is activated, occasion of NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting. If the higher layer parameter timeRestrictionForInterferenceMeasurements is set to "notConfigured", the UE shall derive the interference measurements for computing CSI value reported in uplink slot n based on only the CSI-IM and/or NZP CSI-RS for interference measurement no later than the CSI reference resource associated with the CSI resource setting. If the higher layer parameter timeRestrictionForInterferenceMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the interference measurements for computing the CSI value reported in uplink slot n based on the most recent, no later than the CSI reference resource, in cell DTX active time if cell DTX is activated, occasion of CSI-IM and/or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) associated with the CSI resource setting. < Unchanged parts are omitted > --------------------------------------- End of Text Proposal ---------------------------------- |
Agreement
TP #6-1 (TS38.213)
|
Reasons for change: There are multiple types of CSS, and specification unclear which CSS could be applicable for DCI format 2-9. |
|
Summary of change: Specify DCI format 2-9 uses Type 3 CSS. |
|
Consequences if not adopted: Ambiguous specification. |
|
11.5 Adaptation of cell operation A UE configured for operation on a serving cell according to one or both of a cell DTX operation by cellDTXConfig and a cell DRX operation by cellDRXConfig for the serving cell [11, TS 38.331], can be additionally provided by dci-Format2-9 a search space set to monitor PDCCH for detection of DCI format 2_9 according to a Type3-PDCCH common search space as described in clause 10.1, and a location in DCI format 2_9 by position-inDCI-NES of a cell DTX/DRX indicator field for the serving cell *** Unchanged parts are omitted *** |
R1-2310454 Discussion summary #5 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in Friday session.
[115-R18-NES] – Yi (Huawei)
Email discussion on NR network energy savings
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2310863 Maintenance of CSI enhancements for NES Huawei, HiSilicon
R1-2310985 Techniques in spatial and power domains Nokia, Nokia Shanghai Bell
R1-2310993 Discussion on NES techniques in spatial and power domains ZTE, Sanechips
R1-2311051 Remaining details on NW energy saving techniques in spatial and power domains Fujitsu
R1-2311102 Remaining issues on NES techniques in spatial and power domain vivo
R1-2311137 Maintenance issues of NES spatial and power domain operations Intel Corporation
R1-2311170 Remaining issues on NES techniques in spatial and power domains Spreadtrum Communications
R1-2311243 Discussion on remaining issue for techniques in spatial and power domains OPPO
R1-2311347 Network Energy Saving techniques in spatial and power domain CATT
R1-2311358 Remaining issues on Spatial NES FUTUREWEI
R1-2311413 Remaining issues on NES techniques in spatial and power domains Beijing Xiaomi Mobile Software
R1-2311487 Remaining issues on spatial and power domains enhancements for network energy saving CMCC
R1-2311509 Remaining issues on network energy saving techniques in spatial and power domains NEC
R1-2311535 Remaining issues on NES techniques in spatial and power domains InterDigital, Inc.
R1-2311546 Remaining issues on CSI enhancement for NES China Telecom
R1-2311574 Network Energy Saving in Spatial and Power Domain Google
R1-2311656 Maintenance of spatial and power domain enhancements for NW energy savings NTT DOCOMO, INC.
R1-2311689 On remaining issues for spatial and power domain enhancements to support network energy saving Apple
R1-2311763 Remaining issues of spatial and power domain adaptation for network energy saving Panasonic
R1-2311798 Remaining issues of NES techniques in spatial and power domains Transsion Holdings
R1-2311849 Remaining issues on NES techniques in spatial and power domains Samsung
R1-2311895 Remaining issues of NES techniques in spatial and power domains LG Electronics
R1-2311933 Remaining issues on techniques in spatial and power domains Ruijie Network Co. Ltd
R1-2311938 Maintenance on Network energy saving techniques in spatial and power domains Lenovo
R1-2311980 Maintenance on NES techniques in spatial and power domains MediaTek Inc.
R1-2312041 Remaining aspects of spatial and power domain adaptation Qualcomm Incorporated
R1-2312100 Maintenance of NW energy saving techniques in spatial and power domains Ericsson
R1-2312113 Correction on spatial adaptation ASUSTeK
R1-2312159 Remaining issues on techniques in spatial and power domains CEWiT
R1-2312346 FL summary#1 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Monday session
Agreement
Report quantities of 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP- Index', 'ssb-Index-SINR- Index' or 'tdcp' are NOT applicable to Rel-18 NES.
Agreement (further amended in Friday session as shown in red)
· For Type 2 SD adaptation or joint operation of Type 2 SD and PD adaptation,
o
It
is up to gNB configuration whether or not the list of NZP CSI-RS resources
configured for a sub-configuration is identical to or has no intersection with
the list of NZP CSI-RS resources configured for the other sub-configuration(s)
within the same CSI-ReportConfig.
o The non-PMI-PortIndication, or typeISinglePanel-codebookSubsetRestriction-i2 can be configured in CSI-ReportConfig instead of in sub-configuration.
Agreement
· CSI-IM is supported for Rel-18 NES without need of spec update, i.e. resource-wise association is maintained between NZP CSI-RS for CM and CSI-IM.
· NZP CSI-RS for IM is supported for Rel-18 NES.
o Above applies only for the case of PD only adaptation with a single CSI-RS resource for channel measurement.
R1-2312347 FL summary#2 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Tuesday session
Agreement
When the report setting is configured with report quantity other than CRI-RI-CQI, for a CSI report containing Type 1 SD sub-configuration(s), support port re-indexing to enable consecutive port indices for CQI calculation purpose.
Agreement
For Type 2 SD only,
·
The list of NZP CSI-RS resources is identical to or has no intersection with the
list of NZP CSI-RS resources configured for any other sub-configuration(s)
within the CSI-ReportConfig.
Agreement
For Type 1 SD adaptation, or joint operation of Type 1 SD and PD adaptation,
· For a CSI report with reportQuantity set to 'cri-RI-i1-CQI', UE expects that typeISinglePanel-codebookSubsetRestriction-i2 to be configured in each sub-configuration that contains port-subsetIndicator.
· If there is at least one sub-configuration corresponding to 'typeI-SinglePanel' and at least one sub-configuration corresponding to 'typeI-MultiPanel' in the same CSI report configuration, UE expects that codebookMode to be configured in each sub-configuration that contains port-subsetIndicator.
Agreement
For Type 1 SD adaptation, or joint operation of Type 1 SD and PD adaptation, for a CSI report with reportQuantity set to 'cri-RI-CQI',
· UE expects that non-PMI-PortIndication, if configured, to be configured in each sub-configuration containing port-subsetIndicator.
o Ports selected in the non-PMI-PortIndication correspond to enabled ports in the bitmap port-subsetIndicator.
· If non-PMI-PortIndication is not configured in a sub-configuration, UE applies legacy behavior for the case where non-PMI-PortIndication is not configured after re-indexing CSI-RS port indices, by replacing P with the number of enabled ports in the bitmap port-subsetIndicator configured for the sub-configuration.
R1-2312348 FL summary#3 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Wednesday session
Conclusion
For CSI report with multiple sub-configurations,
· When a CSI report with only one part/part 1 CSI is determined as the lowest priority and to be omitted, the one part/part1 CSI corresponding to all sub-configurations is dropped together
R1-2312349 FL summary#4 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Thursday session
Agreement
Adopt the following TP for TS 38.214
|
Reason for change: · The definition of X sub-configuration is not clear. · The SD and PD joint operation case Is not counted |
|
Summary of change: · Clarified the definition of X sub-configurations. · Added the counting rule for consideration of SD and PD joint operation |
|
Consequences if not approved: · The result of CSI-RS resource/port counting for CSI report configuration containing sub-configurations is not clear. · The counting rule is not clear when PD adaptation is jointly operated |
|
-----------------------------------------------------------Text proposal ----------------------------------------------------------- 5.2.1.6 CSI processing criteria <omitted text> In
any slot, the UE is not expected to have more active CSI-RS ports or active
CSI-RS resources in active BWPs than reported as capability. NZP CSI-RS
resource is active in a duration of time defined as follows. For aperiodic
CSI-RS, starting from the end of the PDCCH containing the request and ending
at the end of the scheduled PUSCH containing the report associated with this
aperiodic CSI-RS. When the PDCCH candidates are associated with a search
space set configured with searchSpaceLinking,
for the purpose of determining the NZP CSI-RS resource active
duration, the PDCCH candidate that ends later in
time among the two linked PDCCH candidates is used. For
semi-persistent CSI-RS, starting from the end of when the activation command
is applied, and ending at the end of when the deactivation command is
applied. For periodic CSI-RS, starting when the periodic CSI-RS is configured
by higher layer signalling, and ending when the periodic CSI-RS configuration
is released. If a CSI-RS resource is referred N times by one or more
CSI Reporting Settings not configured with higher
layer parameter [csi-ReportSubConfigList], the CSI-RS resource
and the CSI-RS ports within the CSI-RS resource are counted N times.
For a CSI-RS Resource Set for channel
measurement configured with two Resource Groups and For a
Where
P
is
the number of ports configured by nrofPorts and <omitted text> -------------------------------------------------------End of Text proposal ------------------------------------------------------ |
Agreement
Adopt the following TP from [Docomo] for TS 38.214 Clause 5.2.1.4.2
|
· Reason for changes: o There is no description on the mapping between CRI and CSI-RS resource for a sub-configuration configured with CSI-RS ID list · Summary of changes: o Add the mapping between CRI and CSI-RS resource for a sub-configuration configured with CSI-RS ID list · Consequences if not approved o The mapping between CRI and CSI-RS resource for a sub-configuration configured with CSI-RS ID list is unclear <omitted texts> If the UE is configured with a CSI-ReportConfig that contains a list of sub-configurations, provided by the higher layer parameter [csi-ReportSubConfigList]: - the UE expects to be configured with the higher layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. If the UE indicates a capability for supporting mixed codebook combination in a slot with [ABC], each sub-configuration can be configured with the higher layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. - Each sub-configuration can be
configured with an antenna port subset using the higher layer bitmap
parameter [port-subsetIndicator] which contains the bit sequence - If a sub-configuration is configured with an antenna port subset, then the sub-configuration can be configured with a [RI restriction parameter] and, if the number of antenna ports of the subset greater than 2, with [n1-n2 parameter] if the higher layer parameter codebookType is set to 'typeI-SinglePanel' or with [ng-n1-n2 parameter] if the higher layer parameter codebookType is set to 'typeI-MultiPanel', and, if the corresponding number of antenna ports of the subset is 2, with twoTX-CodebookSubsetRestriction, where the parameters [RI restriction], [n1-n2], [ng-n1-n2], twoTX-CodebookSubsetRestriction are as described in Clauses 5.2.2.2.1 and 5.2.2.2.2. - A sub-configuration can be configured with a list of NZP CSI-RS resources, provided by [nzp-CSI-RS-resourceList], which indicates one or more NZP CSI-RS resources, within the NZP-CSI-RS-ResourceSet contained in the CSI-ResourceConfig for channel measurement which corresponds to the CSI-ReportConfig. [The list of NZP CSI-RS resources is identical to or has no intersection with a list of NZP CSI-RS resources configured for any other sub-configuration(s) within the CSI-ReportConfig.] - If a sub-configuration is configured with a list of NZP CSI-RS resources with more than one resources, the UE shall derive the CSI parameters other than CRI conditioned on the reported CRI, where the CRI k (k ≥ 0) for the sub-configuration corresponds to the configured (k+1)-th entry of associated nzp-CSI-RS-Resources in the list of NZP CSI-RS resources. - A sub-configuration can be configured with a power offset provided by [powerOffset]. - If a sub-configurations is not configured with [nzp-CSI-RS-resourceList] then the sub-configuration shall be associated with all the NZP CSI-RS resources within the NZP-CSI-RS-ResourceSet contained in the CSI-ResourceConfig for channel measurement which corresponds to the CSI-ReportConfig. - the UE reports CSI(s) for one or more sub-configurations according to Clauses 5.2.1.5.1, 5.2.1.5.2, 5.2.3 and 5.2.4, and according to the higher layer parameter reportQuantity configured for that CSI-ReportConfig. <omitted texts> |
Agreement
For CPU occupation time for CSI report with one or more sub-configurations,
· For periodic CSI report which contains a list of sub-configurations,
o It
occupies CPU(s) from the first symbol of the earliest one of each CSI-RS/CSI-IM/SSB
resource for channel or interference measurement within all L configured
sub-configurations, respective latest CSI-RS/CSI-IM/SSB occasion no
later than the corresponding CSI reference resource, until the last symbol of
the configured PUSCH/PUCCH carrying the report.
· For semi-persistent CSI report on PUSCH (excluding an initial semi-persistent CSI report on PUSCH after the PDCCH triggering the report) or semi-persistent CSI report on PUCCH which contains a list of sub-configurations
o
It occupies CPU(s) from the first symbol of
the earliest one of each CSI-RS/CSI-IM/SSB resource for channel or
interference measurement within N triggered
sub-configurations, until the last symbol of the configured
PUSCH/PUCCH carrying the report.
For CSI computation time (Z2, Z2’),
· For a CSI-ReportConfig with sub-configurations, the definition of the corresponding CSI computation time is based on the CSI-RS resources for channel measurement, the CSI-RS resources for interference measurement and the CSI-IM resources for all triggered sub-configurations for AP-CSI report.
Editors to draft TP if needed.
Conclusion
The powerControlOffset configured in TRS still indicates the power offset between PDSCH and TRS.
· New L1 signalling is not introduced.
· No spec impact is needed.
Conclusion
NC-JT operation is not applicable for Rel-18 NES.
· No further spec impact is needed.
Agreement
Adopt the following TP for 38.214, Section 5.2.3 and 5.2.4
|
· Reason for changes o Terminology of CSIs between 38.214 and 38.212 is misaligned for the description of CSI Part 2 omission · Summary of changes o Change “CSIs” in 38.214 to “CSI sub-reports” · Consequences if not approved o Inconsistent terminology between different specifications for description of CSI Part 2 omission
-------------------------------- Text Proposal for 38.214, Section 5.2.3 and 5.2.4 ----------------------------------- 5.2.3 CSI reporting using PUSCH *** Unchanged text omitted *** For both Type I and Type II reports configured for PUCCH but transmitted on PUSCH, the determination of the payload for CSI part 1 and CSI part 2 follows that of PUCCH as described in Clause 5.2.4. When CSI reporting on PUSCH comprises two parts, the UE may omit
a portion of the Part 2 CSI. Omission of Part 2 CSI is according to the
priority order shown in Table 5.2.3-1, where *** Unchanged text omitted *** - For
a Reporting Setting for which the CSI-ReportConfig contains a list of
sub-configurations provided by the higher layer parameter [csi-ReportSubConfigList],
for a corresponding CSI report *** Unchanged text omitted *** 5.2.4 CSI reporting using PUCCH *** Unchanged text omitted *** If
any of the CSI reports consist of two parts, the UE may omit a portion of
Part 2 CSI. Omission of Part 2 CSI is according to the priority order shown
in Table 5.2.3-1. For a Reporting Setting for which the CSI-ReportConfig
contains a list of sub-configurations provided by the higher layer parameter
[csi-ReportSubConfigList], for a given CSI report which contains one
or more CSI *** Unchanged text omitted *** ----------------------------------------------------------- End Text Proposal --------------------------------------------------------- |
Agreement
For a CSI report configuration containing a list of sub-configurations, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report including one or more sub-reports only after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement, per sub-configuration, no later than CSI reference resource and drops the report otherwise.
For the above “per sub-configuration”, it is a sub-configuration that is
· Alt 1: the activated/triggered one for SP-CSI reporting
R1-2312638 FL summary#5 for SD and PD adaptation for R18 NES Moderator (Huawei)
From Friday session
Agreement
Adopt the following TP for TS 38.214, 5.2.1.4.2
|
· Reason for changes: o The Rel-18 spec in Section 5.2.1.4.2 seems to limit a CSI-ReportConfig to be associated with only a single CSI-RS resource set the due to the word “the” in the text · Summary of changes: o Remove the restriction for the association of single resource set · Consequences if not approved o The association of resource set and reportConfig is single, which is against legacy function 5.2.1.4.2 Report quantity configurations *** Text omitted *** If the UE is configured with a CSI-ReportConfig that contains a list of sub-configurations, provided by the higher layer parameter [csi-ReportSubConfigList]: - the UE expects to be configured with the higher layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. If the UE indicates a capability for supporting mixed codebook combination in a slot with [ABC], each sub-configuration can be configured with the higher layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. - Each
sub-configuration can be configured with an antenna port subset using the
higher layer bitmap parameter [port-subsetIndicator] which contains
the bit sequence - If a sub-configuration is configured with an antenna port subset, then the sub-configuration can be configured with a [RI restriction parameter] and, if the number of antenna ports of the subset greater than 2, with [n1-n2 parameter] if the higher layer parameter codebookType is set to 'typeI-SinglePanel' or with [ng-n1-n2 parameter] if the higher layer parameter codebookType is set to 'typeI-MultiPanel', and, if the corresponding number of antenna ports of the subset is 2, with twoTX-CodebookSubsetRestriction, where the parameters [RI restriction], [n1-n2], [ng-n1-n2], twoTX-CodebookSubsetRestriction are as described in Clauses 5.2.2.2.1 and 5.2.2.2.2. - A
sub-configuration can be configured with a list of NZP CSI-RS resources,
provided by [nzp-CSI-RS-resourceList], which indicates one or more NZP
CSI-RS resources, within [The list of NZP CSI-RS resources is identical to or has no intersection with a list of NZP CSI-RS resources configured for any other sub-configuration(s) within the CSI-ReportConfig.] - A sub-configuration can be configured with a power offset provided by [powerOffset]. - If a sub-configuration - the UE reports CSI(s) for one or more sub-configurations according to Clauses 5.2.1.5.1, 5.2.1.5.2, 5.2.3 and 5.2.4, and according to the higher layer parameter reportQuantity configured for that CSI-ReportConfig. *** Text omitted *** |
Final summary in R1-2312639.
R1-2310864 Maintenance of Cell DTX/DRX for NES Huawei, HiSilicon
R1-2310986 Enhancements on cell DTX/DRX mechanism Nokia, Nokia Shanghai Bell
R1-2310994 Discussion on cell DTX/DRX ZTE, Sanechips
R1-2311052 Remaining details on cell DTX DRX mechanism Fujitsu
R1-2311103 Remaining issues on enhancements on cell DTX/DRX mechanism vivo
R1-2311138 Maintenance issues of NES cell DTX/DRX operations Intel Corporation
R1-2311171 Remaining issues on enhancements on cell DTX/DRX mechanism Spreadtrum Communications
R1-2311244 Discussion on remaining issue for enhancements on cell DTX/DRX mechanism OPPO
R1-2311348 DTX/DRX for network Energy Saving CATT
R1-2311359 Remaining Issues on Cell DTX/DRX FUTUREWEI
R1-2311407 Discussions on cell DTX-DRX for network energy saving xiaomi
R1-2311488 Remaining issues on cell DTX DRX mechanism for NES CMCC
R1-2311511 Remaining issues on cell DTX/DRX configuration for Network Energy Saving NEC
R1-2311536 Remaining issues on cell DTX/DRX mechanism InterDigital, Inc.
R1-2311547 Remaining issues on mechanism of Cell DTX/DRX China Telecom
R1-2311575 Network Energy Saving on Cell DTX and DRX Google
R1-2311627 Maintenance on enhancements on Cell DTX/DRX mechanism NTT DOCOMO, INC.
R1-2311690 On remaining issues for cell DTX/DRX mechanism Apple
R1-2311754 Remaining issues on cell DTX/DRX mechanism ETRI
R1-2311764 Remaining issues of Cell DTX/DRX enhancement for network energy saving Panasonic
R1-2311799 Remaining issues on enhancement on cell DTXDRX mechanism Transsion Holdings
R1-2311850 Remaining issues on cell DTX/DRX mechanism Samsung
R1-2311896 Remaining issues of cell DTX/DRX mechanism LG Electronics
R1-2311939 Maintenance on enhancements on cell DTX/DRX mechanism Lenovo
R1-2311981 Maintenance on cell DTX/DRX mechanism MediaTek Inc.
R1-2312042 Remaining aspects of cell DTX and DRX Qualcomm Incorporated
R1-2312101 Maintenance for cell DTX/DRX Ericsson
R1-2312112 Correction on cell DTX DRX ASUSTeK
R1-2312161 Discussion on cell DTX/DRX mechanism CEWiT
R1-2312313 Summary of maintenance issues for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
R1-2312314 Discussion summary #1 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Monday session
Agreement
Agreement
|
Reason for change: The parameter that defines cell DTX/DRX patterns in RAN1 spec does not align with RAN2 running CR. |
|
Summary of change: Align parameter name with RAN2 . |
|
Consequences if not approved: Unmatched specs. |
|
*** Unchanged parts are omitted *** 11.5 Adaptation of cell operation A
UE configured for operation on a serving cell according to one or both of a cell DTX operation 1 - if the UE is configured with both cell DTX operation and cell DRX operation for the serving cell, the cell DTX/DRX indicator field includes two bits where the first bit indicates the cell DTX operation and the second bit indicates the cell DRX operation 2 - if the UE is configured with only one of the cell DTX operation and cell DRX operation for the serving cell, the cell DTX/DRX indicator field includes one bit indicating one of the cell DTX operation and cell DRX operation, respectively, for the serving cell 3 - a '0' value for a bit of the cell DTX/DRX indicator field indicates deactivation of cell DTX or of cell DRX 4 - a '1' value for a bit of the cell DTX/DRX indicator field indicates activation of cell DTX or of cell DRX 5 - if the serving cell is configured with a SUL carrier, the cell DTX/DRX indicator field indication for activation or deactivation of cell DRX applies to both the UL carrier and the SUL carrier A UE does not expect to monitor PDCCH for detection of DCI format 2_9 on more than one serving cells. *** Unchanged parts are omitted *** |
Agreement
UE transmits a subset of the repetitions in a CG bundle that do not overlap with the cell DRX non-active period.
Agreement
|
Agreement Cell DTX/DRX operation is only supported for sTRP. |
R1-2312409 LS on Cell DTX/DRX operations for sTRP RAN1, Intel Corporation
Wednesday decision: The LS is approved.
R1-2312315 Discussion summary #2 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Tuesday session
Agreement
UE is expected to monitor DCI format 2_9 during active periods of C-DRX.
Conclusion
There is no consensus in RAN1 on whether or not the UE is expected to monitor DCI format 2_9 during non-active periods on C-DRX.
R1-2312410 Discussion summary #3 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Presented in Tuesday session
R1-2312411 Discussion summary #4 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Wednesday session
Agreement
Adopt the following specification change in TS38.213
------------ Start of TP -----------
11.5 Adaptation of cell operation
A UE does not expect to monitor PDCCH for detection of DCI format 2_9 on more than one serving cells in one cell group.
*** Unchanged parts are omitted ***
------------ End of TP -----------
Agreement
· For Cell DTX/DRX indication of a block in DCI format 2_9
o if [cellDTXDRX-L1activation] is configured,
§ 2 bits if cellDTXDRXconfigType is configured to dtxdrx for the serving cell;
§ 1 bit if cellDTXDRXconfigType is configured to either dtx or drx for the serving cell;
o otherwise 0 bit.
o [cellDTXDRX-L1activation] is a new RRC parameter
Agreement
· Introduce a new RRC parameter [cellDTXDRX-L1activation], that indicates configuration of L1 based cell DTX/DRX activation/deactivation for each serving cell.
· Adopt the follow TP for TS38.212
|
Reason for change: Clarify that 2 bits are needed if both cell DTX and cell DRX are configured for a serving cell; otherwise (i.e. only one cell DTX or cell DRX is configured), 1 bit is needed which corresponds to cell DTX or cell DRX configuration activation/deactivation and if not cell DTX and DRX is not configured 0 bits. Clarify that 1 bit for NES mode indication if configured by higher layers. Update RRC parameter names in the specification. |
|
Summary of change: · update NES-RNTI as cellDTRX-RNTI. · Associate the starting position of a block in DCI format 2_9 with a serving cell. · clarify the bitwidth of dynamic cell DTX/DRX information field in DCI format 2_9. · add NES-mode indication to block definition. |
|
Consequences if not approved: The starting position and bitwidth of dynamic cell DTX/DRX information field in DCI format 2_9 is unclear. NES-mode indication associated with nesEvent configuration is missing from specification. |
|
7.3.1.3.10 Format 2_9 DCI format 2_9 is used for activating or de-activating the cell DTX and/or DRX configuration of one or multiple serving cells for one or more UEs and/or to provide NES-mode indication. The following information is transmitted by means of the
DCI format 2_9 with CRC scrambled by - block number 1, block number 2,…, block number N where the starting position of a block associated with a serving cell is determined by the parameter positionInDCI-cellDTRX provided by higher layers for the UE. If
the UE is configured - Cell DTX/DRX indication – - if [cellDTXDRX-L1activation]
is configured, 2
bits if - otherwise 0 - NES-mode indication – 1 bit if nesEvent is configured and the serving cell is Pcell; otherwise, 0 bit.
The size of DCI format 2_9 is indicated by the higher layer parameter sizeDCI-2-9. *** Unchanged parts are omitted *** |
Agreement
Adopt the following TP for TS38.213
|
Reasons for change: Unclear how HARQ feedback for cancelled SPS PDSCH in cell DRX/DRX operation should be handled by specification. Summary of change: Clarify that HARQ feedback of cancelled SPS PDSCH by non-active period of cell DTX is not transmitted by UE. Consequences if not adopted: Incomplete specification |
|
9.1.2 Type-1 HARQ-ACK codebook determination *** Unchanged text omitted *** In the following pseudo-code, SPS PDSCH receptions associated with a SPS PDSCH configuration are activated by a DCI format with CRC scrambled by a CS-RNTI or by a DCI format with CRC scrambled by a G-CS-RNTI. Set
Set
Set
Set
Set
while
Set while
Set
while
if { a UE is configured to
receive SPS PDSCHs from slot HARQ-ACK information for the SPS PDSCH is associated with the PUCCH }
end if
end while
end while
end while *** Unchanged text omitted *** |
R1-2312412 Discussion summary #5 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Thursday session
Agreement
· Adopt the follow TP for TS38.213
|
Reasons for change: TS38.331 specification does not provide the definition of 0 or 1 for NES-mode indication and is current missing from 3GPP specification. Field naming between TS38.212 and TS38.213 is not consistent. Summary of change: Clarify that 0 refers to NES-specific CHO execution condition is not met, and 1 refers to condition met. Align the field names between TS38.212 and TS38.213. Consequence if not adopted: Incomplete specifications. |
|
11.5 Adaptation of cell operation A
UE configured for operation on a serving cell according to one or both of a
cell DTX operation by cellDTXConfig and a cell DRX operation by cellDRXConfig
for the serving cell [11, TS 38.331], can be
additionally provided by dci-Format2-9 a search space set to monitor
PDCCH for detection of DCI format 2_9 according to a common
search space as described in clause 10.1, and a location
in DCI format 2_9 by - if
the UE is configured with both cell DTX operation and cell DRX operation for
the serving cell and if [cellDTXDRX-L1activation]
is configured, the cell DTX/DRX indication - if
the UE is configured with only one of the cell DTX operation and cell DRX
operation for the serving cell, the cell DTX/DRX indication - a
'0' value for a bit of the cell DTX/DRX indication - a
'1' value for a bit of the cell DTX/DRX indication - if nesEvent is configured, the NES-mode indication field includes one bit indicating NES-specific CHO execution condition, as described in [12, TS 38.331] - a ‘0’ value for a bit of the NES-mode indication field, indicates NES-specific CHO execution condition is disabled [12, TS 38.331] a '1' value for a bit of the NES-mode indication field, indicates NES-specific CHO execution condition is enabled [12, TS 38.331] |
Agreement
· Adopt the following TP for TS38.214
|
Reasons for change: For a CSI reporting, the most recent CSI-RS measurement occasion is unclear when cell DTX is activated by RRC or DCI format 2-9. Summary of change: When cell DTX is activated by RRC or DCI format 2-9, the most recent CSI-RS measurement occasion occurs in active period of cell DTX. Consequences if not approved: For a CSI reporting, the most recent CSI-RS measurement occasion is unclear when cell DTX is activated. |
|
5.1.6.1 CSI-RS reception procedure < Unchanged parts are omitted > If the UE is configured with DRX, - if the UE is configured to monitor DCI format 2_6 and configured by higher layer parameter ps-TransmitOtherPeriodicCSI to report CSI with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to quantities other than 'cri-RSRP' and 'ssb-Index-RSRP' when drx-onDurationTimer in DRX-Config is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by drx-onDurationTimer in DRX-Config also outside DRX active time for CSI to be reported; - if the UE is configured to monitor DCI format 2_6 and configured by higher layer parameter ps-TransmitPeriodicL1-RSRP to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to cri-RSRP when drx-onDurationTimer in DRX-Config is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by drx-onDurationTimer in DRX-Config also outside DRX active time for CSI to be reported; - otherwise, the most recent CSI measurement occasion occurs in active time for CSI to be reported. During non-active periods of cell DTX, the UE configured with cell DTX is not expected to receive the periodic CSI-RS and semi-persistent CSI-RS configured in CSI report configuration in CSI-ReportConfig associated with the higher layer parameter reportQuantity comprising at least ‘RI’. If the cell DTX is activated, the most recent CSI measurement occasion of semi-persistent CSI-RS resource or periodic CSI-RS resource occurs in active periods of cell DTX for CSI report configured by CSI-ReportConfig associated with the higher layer parameter reportQuantity comprising at least ‘RI’. < Unchanged parts are omitted > |
Agreement
If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH(s) and PUSCH(s) in a slot, where at least one PUCCH/PUSCH overlaps with non-active periods of cell DRX on the respective serving cell, down-select form the following options for the interaction between the Operation A (Resolve the overlapping among PUCCHs/PUSCHs (TS 38.213 clause 9 including sub-clauses)) and Operation B (Determine whether to transmit a PUCCH/PUSCH overlapping with non-active period of cell DRX).
· Option 1: UE first performs Operation A and then performs Operation B.
R1-2312606 Discussion summary #6 for enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
From Friday session
Agreement
|
· Reason for change: The order of resolving overlapping PUCCH(s) and/or PUSCH(s) and performing cell DRX operation is not clear in spec. · Summary of change: First resolving overlapping PUCCH(s) and/or PUSCH(s) and then performing cell DRX operation · Consequences if not approved: The order of resolving overlapping PUCCH(s) and/or PUSCH(s) and performing cell DRX operation is not defined in spec. |
|
9 UE procedure for reporting control information *** Unchanged text is omitted *** When a UE determines overlapping for PUCCH and/or PUSCH transmissions of the same priority index other than PUCCH transmissions with SL HARQ-ACK reports before considering limitations for UE transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2, including repetitions if any, - first, the UE resolves the overlapping for PUCCHs with repetitions as described in clause 9.2.6, if any - second, the UE resolves the overlapping for PUCCHs without repetitions as described in clauses 9.2.5 - third, the UE resolves the overlapping for PUSCHs and PUCCHs with repetitions as described in clause 9.2.6 - fourth, the UE resolves the overlapping for PUSCHs and PUCCHs without repetitions as is subsequently described in this clause. If a UE - is provided simultaneousPUCCH-PUSCH and would transmit a PUCCH with a first priority index and PUSCHs with a second priority index that is different than the first priority index, where the PUCCH and the PUSCHs overlap in time - can simultaneously transmit the PUCCH and the PUSCHs [18, TS 38.306], the UE excludes the PUSCHs for resolving the time overlapping between the PUCCH and PUSCHs, where the timeline conditions are not required for the excluded PUSCHs. When a UE determines overlapping for PUCCH and/or PUSCH transmissions of different priority indexes, other than PUCCH transmissions with SL HARQ-ACK reports, before considering limitations for transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2, including repetitions if any, if the UE is provided uci-MuxWithDiffPrio and the timeline conditions in clause 9.2.5 for multiplexing UCI in a PUCCH or a PUSCH are satisfied *** Unchanged text is omitted *** When a UE determines overlapping for PUCCH and/or PUSCH transmissions of different priority indexes, other than PUCCH transmissions with SL HARQ-ACK reports, before considering limitations for transmissions including with repetitions, if any, due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2, if the UE is not provided uci-MuxWithDiffPrio, the UE first resolves overlapping for PUCCH and/or PUSCH transmissions of smaller priority index as described in clauses 9.2.5 and 9.2.6. Then, - if a transmission of a first PUCCH of larger priority index scheduled by a DCI format in a PDCCH reception would overlap in time with a repetition of a transmission of a second PUSCH or a second PUCCH of smaller priority index, the UE cancels the repetition of a transmission of the second PUSCH or the second PUCCH before the first symbol that would overlap with the first PUCCH transmission - if a transmission of a first PUSCH of larger priority index scheduled by a DCI format in a PDCCH reception would overlap in time with a repetition of the transmission of a second PUCCH of smaller priority index, the UE cancels the repetition of the transmission of the second PUCCH before the first symbol that would overlap with the first PUSCH transmission where - the overlapping is applicable before or after resolving overlapping among channels of larger priority index, if any, as described in clauses 9.2.5 and 9.2.6 - any remaining PUCCH and/or PUSCH transmission after overlapping resolution is subjected to the limitations for UE transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2, - the
UE expects that the transmission of the first PUCCH or the first PUSCH,
respectively, would not start before - *** Unchanged text is omitted *** In the remaining of this clause, a UE multiplexes UCIs with same priority index in a PUCCH or a PUSCH before considering limitations for UE transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2. A PUCCH or a PUSCH is assumed to have a same priority index as a priority index of UCIs a UE multiplexes in the PUCCH or the PUSCH. *** Unchanged text is omitted *** |
Final summary in R1-2312607.
[116-R18-NES] – Yi (Huawei)
Email discussion on NR network energy savings
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2400122 Maintenance of Rel-18 NES Huawei, HiSilicon
R1-2400183 Maintenance on Network Energy Savings for NR Nokia, Nokia Shanghai Bell
R1-2400220 Maintenance on Rel-18 network energy saving vivo
R1-2400372 Maintenance issues on NES Intel Corporation
R1-2400391 Maintenance on NES Google
R1-2400410 Remaining Issues in Rel-18 Network Energy Saving CATT
R1-2400485 Remaining issues on Rel-18 NES techniques ZTE, Sanechips
R1-2400540 Remaining issues on network energy saving xiaomi
R1-2400588 Discussion on maintenance on network energy saving for NR OPPO
R1-2400709 Remaining issues on network energy saving Samsung
R1-2400900 Remaining issues of Rel-18 network energy saving Panasonic
R1-2400990 Maintenance of Network Energy Savings for NR Apple
R1-2401139 Maintenance for Rel-18 network energy savings Ericsson
R1-2401185 Correction on cell DTX DRX ASUSTeK
R1-2401186 Maintenance of UE procedure for determining physical downlink control channel assignment ITRI
R1-2401316 Maintenance on Network Energy Savings for NR MediaTek Inc.
R1-2401322 Remaining issues on NES LG Electronics
R1-2401419 Maintenance on cell DTX and DRX Qualcomm Incorporated
R1-2401533 FLS#1 for maintenance of SD-PD adaptation R18 NES Moderator (Huawei)
From Tuesday session
Agreement
· Adopt the following TP for TS 38.214:
|
Reason for change: There is ambiguity on whether the current spec supports sub-configuration level of Part 2 wideband CSI omission. |
|
Summary of change: Omission of Part 2 wideband CSI when needed, is done as legacy in report level. Only Part subband CSI is dropped in sub-configuration level. |
|
Consequences if not approved: UE omission behaviour for Part 2 WB CSI is unclear and unnecessarily complicated, if it is interpreted as supported. |
|
-----------------------------------------------------------Text proposal ----------------------------------------------------------- 5.2.3 CSI reporting using PUSCH <Unchanged parts omitted> When CSI reporting on PUSCH comprises two parts, the UE may omit
a portion of the Part 2 CSI. Omission of Part 2 CSI is according to the
priority order shown in Table 5.2.3-1, where
- For a Reporting Setting for which the CSI-ReportConfig contains a list of sub-configurations provided by [csi-ReportSubConfigList], for a corresponding CSI report which contains one or more CSIs sub-reports, omission of Part 2 subband CSI is done at a sub-configuration level within the same priority level defined by Table 5.2.3-1 where a sub-configuration with an index, provided by [csi-ReportSubConfigID], with lower value has higher priority. <Unchanged parts omitted> -------------------------------------------------------End of Text proposal ------------------------------------------------------ |
Agreement
· Adopt the following TP for clause 5.2.1.4.2 of TS 38.214.
|
Reason for change: For non-PMI feedback in type-1 SD, the value of P is not defined. Summary of change: For non-PMI feedback in type-1 SD, the value of P is same as the legacy, i.e. {1, 2, 4, 8}. Consequence if not approved: The value of P in non-PMI feedback in type-1 SD is not clear. ---------------------------- Start of Text Proposal for TS 38.214 ----------------------------- 5.2.1.4.2 Report quantity configurations < Unchanged parts are omitted > If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-CQI', - if the UE is configured
with higher layer parameter non-PMI-PortIndication contained in a CSI-ReportConfig, r ports are
indicated in the order of layer ordering for rank r and each CSI-RS
resource in the CSI resource setting is linked to the CSI-ReportConfig based on the order of
the associated NZP-CSI-RS-ResourceId in the linked CSI resource
setting for channel measurement given by higher layer parameter resourcesForChannelMeasurement.
The configured higher layer parameter non-PMI-PortIndication contains a sequence - if the UE is
not configured with higher layer parameter non-PMI-PortIndication, the UE assumes, for
each CSI-RS resource in the CSI resource setting linked to the CSI-ReportConfig,
that the CSI-RS port indices - When
calculating the CQI for a rank, the UE shall use the ports indicated for that
rank for the selected CSI-RS resource. The precoder for the indicated ports
shall be assumed to be the identity matrix scaled by < Unchanged parts are omitted > --------------------------------------- End of Text Proposal ---------------------------------- |
Agreement
· Adopt the following TP for Subclause 5.2.1.6 in TS 38.214.
|
Reason for changes: The definition of Ps is incorrect for AP-CSI. |
|
Summary of changes: Clarify the definition of Ps. |
|
Consequences if not approved: The counting of active CSI-RS resources/ports for NES is incorrect for AP-CSI. |
|
5.2.1.6 CSI processing criteria <omitted text> For
a CSI-ReportConfig containing a list of L sub-configuration(s)
provided by higher layer parameter csi-ReportSubConfigList, if
a CSI-RS resource is referred by M sub-configurations among N
triggered sub-configurations for CSI reporting for aperiodic CSI-RS resource,
or L configured sub-configurations for CSI reporting for periodic or
semi-persistent CSI-RS resource, the CSI-RS resource is counted M
times and the CSI-RS ports within the CSI-RS resource are counted <omitted text> |
Agreement
· Adopt the following TP for TS 38.214.
|
Reason for change: For CPU occupation for SP-CSI report, the current spec only mentioned the triggered sub-configuration, missing the activated sub-configuration. |
|
Summary of change: Added “activated” to cover the case of SP-CSI on PUCCH |
|
Consequences if not approved: The CPU occupation for SP-CSI activated on PUCCH is not covered by spec |
|
-----------------------------------------------------------Text proposal ----------------------------------------------------------- 5.2.1.6 CSI processing criteria <Unchanged parts omitted> For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity not set to 'none', the CPU(s) are occupied for a number of OFDM symbols as follows: - A periodic or semi-persistent CSI report (excluding an initial semi-persistent CSI report on PUSCH after the PDCCH triggering the report) occupies CPU(s) from the first symbol of the earliest one of each CSI-RS/CSI-IM/SSB resource, or each CSI-RS/CSI-IM resource associated with all configured sub-configurations for periodic CSI report corresponding to a CSI-ReportConfig that contains a list of sub-configurations provided by csi-ReportSubConfigList, or each CSI-RS/CSI-IM resource associated with all activated/triggered sub-configurations for semi-persistent CSI report corresponding to a CSI-ReportConfig that contains a list of sub-configurations provided by csi-ReportSubConfigList, for channel or interference measurement, respective latest CSI-RS/CSI-IM/SSB occasion no later than the corresponding CSI reference resource, until the last symbol of the configured PUSCH/PUCCH carrying the report. <Unchanged parts omitted> -------------------------------------------------------End of Text proposal ------------------------------------------------------ |
Conclusion
The “on the PCell, or on the PSCell, or SCell if applicable as described in [10, TS 38.133] ” in the below texts of TS38.213 sub-clause 4.1 can also refer to the reference serving cell provided by higher layer parameter referenceCell for Rel-18 NES.
· No spec update is needed.
|
---------------------------------------------- 38.213 v18.1.0 sub-clause 4.1 ----------------------------- 4.1 Cell search <unchanged text omitted> For a serving cell without transmission of SS/PBCH blocks, a UE acquires time and frequency synchronization with the serving cell based on receptions of SS/PBCH blocks on the PCell, or on the PSCell, or on an SCell if applicable as described in [10, TS 38.133], of the cell group for the serving cell. <unchanged text omitted> |
Agreement
· Adopt the following TP for TS 38.213.
|
· Reason for changes o Only CMR and IMR and NZP based IMR corresponding to the triggered sub-configurations should be considered for the timeline for reporting multiple UCI types if CSI-ReportConfig contains multiple sub-configurations. · Summary of changes o Clarify that only CMR and IMR and NZP based IMR corresponding to triggered sub-configurations should be considered for the timeline for reporting multiple UCI types if CSI-ReportConfig contains multiple sub-configurations. · Consequences if not approved o Unclear UE behaviors about UE procedure for reporting multiple UCI types if CSI-ReportConfig contains multiple sub-configurations.
9.2.5 UE procedure for reporting multiple UCI types *** Unchanged text is omitted *** If
there is one or more aperiodic CSI reports multiplexed on a PUSCH in the
group of overlapping PUCCHs and PUSCHs and if symbol - the last symbol of aperiodic CSI-RS resource for channel measurements, and - the last symbol of aperiodic CSI-IM used for interference measurements, and - the
last symbol of aperiodic NZP CSI-RS for interference measurements for a CSI-ReportConfig, or for all triggered
sub-configurations if CSI-ReportConfig contains multiple
sub-configurations, when aperiodic CSI-RS is used for channel
measurement for triggered CSI report the
UE is not required to update the CSI report for the triggered CSI
report *** Unchanged text is omitted *** |
R1-2401534 FLS#2 for maintenance of SD-PD adaptation R18 NES Moderator (Huawei)
From Thursday session
Agreement
· Adopt the following TP for TS 38.213:
|
Reason for Change: Whether sub-configuration level omission is supported or not for Part 2 CSI is unclear, however it should be supported as agreed in RAN1 and implemented in other specifications. Summary of Change: Sub-configuration level CSI omission for Part 2 CSI is supported. Consequences if not approved: Unclear UE behavior to perform omission of CSI corresponding to a CSI report configuration containing a list of sub-configurations.
9.2.5.2 UE procedure for multiplexing HARQ-ACK/SR/CSI in a PUCCH For a transmission occasion of a single CSI report, a PUCCH resource is provided by pucch-CSI-ResourceList. For a transmission occasion of multiple CSI reports, corresponding PUCCH resources can be provided by multi-CSI-PUCCH-ResourceList. If a UE is provided first and second PUCCH-Config, multi-CSI-PUCCH-ResourceList is provided by the first PUCCH-Config, and PUCCH-ResourceId in pucch-CSI-ResourceList or multi-CSI-PUCCH-ResourceList indicates a corresponding PUCCH resource in PUCCH-Resource provided by the first PUCCH-Config. If a UE is provided only one PUCCH resource set for transmission of HARQ-ACK information in response to PDSCH reception scheduled by a DCI format or in response to a DCI format having associated HARQ-ACK information without scheduling PDSCH reception, the UE does not expect to be provided simultaneousHARQ-ACK-CSI. A UE is configured by maxCodeRate a code rate for multiplexing HARQ-ACK, SR, and CSI report(s) in a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4. If a UE transmits CSI reports using PUCCH format 2, the UE transmits only wideband CSI for each CSI report [6, TS 38.214]. In the following, a Part 1 CSI report refers either to a CSI report with only wideband CSI or to a Part 1 CSI report with wideband CSI and sub-band CSI. In the following, a Part 2 CSI report refers to a Part 2 CSI sub-report, if a CSI report configuration contains a list of sub-configurations provided by csi-ReportSubConfigList for the Part 2 CSI report [6, TS 38.214]. Denote as - - - - **omitted text** |
Agreement
· Adopt the following TP for TS 38.214:
|
5.2.2.5 CSI reference resource definition After the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report only after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement no later than CSI reference resource and drops the report otherwise. For a CSI report configuration containing a list of sub-configurations provided by csi-ReportSubConfigList, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report including one or more sub-reports only after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement, per sub-configuration, no later than CSI reference resource and drops the report otherwise, where the sub-configuration is the activated/triggered one for AP/SP-CSI reporting, or the configured one for P-CSI reporting. --omitted— When DRX is configured, the UE reports a CSI report only if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement in DRX Active Time no later than CSI reference resource and drops the report otherwise. When DRX is configured, for a CSI report configuration containing a list of sub-configurations provided by csi-ReportSubConfigList, UE reports a CSI report including one or more sub-reports only if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement in DRX Active Time, per sub-configuration, no later than CSI reference resource and drops the report otherwise, where the sub-configuration is the activated/triggered one for AP/SP-CSI reporting, or the configured one for P-CSI reporting. When the UE is configured to monitor DCI format 2_6 and if the UE configured by higher layer parameter ps-TransmitOtherPeriodicCSI to report CSI with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to quantities other than 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index', and 'ssb-Index-RSRP- Index ' when drx-onDurationTimer is not started, the UE shall report CSI during the time duration indicated by drx-onDurationTimer in DRX-Config also outside active time according to the procedure described in Clause 5.2.1.4 if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement during the time duration indicated by drx-onDurationTimer in DRX-Config outside DRX active time or in DRX Active Time no later than CSI reference resource and drops the report otherwise. For a CSI report configuration containing a list of sub-configurations provided by csi-ReportSubConfigList, when the UE is configured to monitor DCI format 2_6 and if the UE configured by higher layer parameter ps-TransmitOtherPeriodicCSI to report CSI with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to quantities other than 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index', and 'ssb-Index-RSRP- Index' when drx-onDurationTimer is not started, UE shall report a CSI report including one or more sub-reports only during the time duration indicated by drx-onDurationTimer in DRX-Config also outside active time according to the procedure described in Clause 5.2.1.4 if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement during the time duration indicated by drx-onDurationTimer in DRX-Config outside DRX active time or in DRX Active Time, per sub-configuration, no later than CSI reference resource and drops the report otherwise, where the sub-configuration is the configured one for P-CSI reporting. When the UE is configured to monitor DCI format 2_6 and if the UE configured by higher layer parameter ps-TransmitPeriodicL1-RSRP to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index', or 'ssb-Index-RSRP- Index' when drx-onDurationTimer is not started, the UE shall report L1-RSRP during the time duration indicated by drx-onDurationTimer in DRX-Config also outside active time according to the procedure described in clause 5.2.1.4 and when reportQuantity set to 'cri-RSRP' or 'cri-RSRP- Index' if receiving at least one CSI-RS transmission occasion for channel measurement during the time duration indicated by drx-onDurationTimer in DRX-Config outside DRX active time or in DRX Active Time no later than CSI reference resource and drops the report otherwise. For the CSI report configuration in CSI-ReportConfig associated with the higher layer parameter reportQuantity comprising at least 'RI' on a serving cell with cell DTX activated [10, TS 38.321], the UE reports a CSI report only if receiving at least one CSI-RS transmission occasion of each periodic CSI-RS resource or semi-persistent CSI-RS resource for channel measurement and/or interference measurement in active periods of cell DTX no later than CSI reference resource, and the UE drops the CSI report otherwise. --omitted— |
Agreement
· Adopt the following TP for TS 38.214:
|
Reason for Change: The restriction on configuring a list of NZP CSI-RS resource IDs for type 2 SD + PD adaptation is not specified. Summary of Change: For type 2 SD + PD adaptation, the NZP CSI-RS resource list configured for a sub-configuration is identical to or has no intersection with the resource list configured for another sub-configuration within the same CSI report configuration. Consequences if not approved: Arbitrary configuration for a list of NZP CSI-RS resource IDs for type 2 SD + PD adaptation is allowed.
5.2.1.4.2 Report quantity configurations <Unchanged texts omitted> If the UE is configured with a CSI-ReportConfig that contains a list of sub-configurations, provided by [csi-ReportSubConfigList]: - The UE expects to be configured with the higher layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. If the UE indicates a capability for supporting mixed codebook combination in a slot with [ABC], each sub-configuration can be configured with the higher layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. - Each sub-configuration can be configured
with an antenna port subset using the higher layer bitmap parameter [port-subsetIndicator]
which contains the bit sequence - If a sub-configuration is configured with an antenna port subset, then the sub-configuration can be configured with a [RI restriction parameter] and, if the number of antenna ports of the subset greater than 2, with [n1-n2 parameter] if the higher layer parameter codebookType is set to 'typeI-SinglePanel' or with [ng-n1-n2 parameter] if the higher layer parameter codebookType is set to 'typeI-MultiPanel', and, if the corresponding number of antenna ports of the subset is 2, with twoTX-CodebookSubsetRestriction, where the parameters [RI restriction], [n1-n2], [ng-n1-n2], twoTX-CodebookSubsetRestriction are as described in Clauses 5.2.2.2.1 and 5.2.2.2.2. If a sub-configuration is configured with an antenna port subset, and if higher layer parameter reportQuantity is set to 'cri-RI-i1-CQI', and if the higher layer parameter codebookType is set to 'typeI-SinglePanel', then the sub-configuration can be configured with higher layer parameter typeI-SinglePanel-codebookSubsetRestriction-i2, where typeI-SinglePanel-codebookSubsetRestriction-i2 is as described in Clause 5.2.2.2.1. - If a sub-configuration is configured with an antenna port subset, and if the CSI-ReportConfig that contains a mix of sub-configuration(s) each corresponding to 'typeI-SinglePanel' some other sub-configuration(s) each corresponding to 'typeI-MultiPanel', then the sub-configuration(s) can be configured with the higher layer parameter codebookMode. - A sub-configuration can be configured with a power offset provided by [powerOffset]. - A sub-configuration can be configured with a list of NZP CSI-RS resources, provided by [nzp-CSI-RS-resourceList], which indicates one or more NZP CSI-RS resources, within a NZP-CSI-RS-ResourceSet contained in the CSI-ResourceConfig for channel measurement which corresponds to the CSI-ReportConfig. If there is no sub-configuration configured with a power offset provided by [powerOffset], the list of NZP CSI-RS resources has no intersection with a list of NZP CSI-RS resources configured for any other sub-configuration(s) within the CSI-ReportConfig, otherwise, the list of NZP CSI-RS resources is identical to or has no intersection with a list of NZP CSI-RS resources configured for any other sub-configuration(s) within the CSI-ReportConfig. - If a sub-configuration is configured with a list of NZP CSI-RS resources with more than one resource, the UE shall derive the CSI parameters other than CRI conditioned on the reported CRI, where the CRI k (k ≥ 0) for the sub-configuration corresponds to the configured (k+1)-th entry of associated NZP-CSI-RS-Resource in the list of NZP CSI-RS resources. - If a sub-configurations is not configured with [nzp-CSI-RS-resourceList] then the sub-configuration shall be associated with all the NZP CSI-RS resources within a NZP-CSI-RS-ResourceSet contained in the CSI-ResourceConfig for channel measurement which corresponds to the CSI-ReportConfig. - the UE reports CSI(s) for one or more sub-configurations according to Clauses 5.2.1.5.1, 5.2.1.5.2, 5.2.3 and 5.2.4, and according to the higher layer parameter reportQuantity configured for that CSI-ReportConfig. - The UE does not expect the higher layer parameter reportQuantity to be set to 'cri-RSRP', 'cri-SINR', 'cri-SINR- Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP- Index', 'ssb-Index-SINR- Index', or 'tdcp'. |
R1-2401502 Summary #1 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Agreement
· Reason of change: the parameter name in RAN1 specification is different from that of in RAN2 specification, while they are assumed to be the same parameter.
· Summary of change: align the parameter name between RAN1 and RAN2 by replacing NES-RNTI with cellDTRX-RNT
· Consequences if not approved: A same parameter being represented by different names in RAN1 and RAN2 specification may cause confusing.
------------ start of TP for TS 38.213-----------------------
10.1 UE procedure for determining physical downlink control channel assignment
<unchanged parts are omitted>
- a Type3-PDCCH CSS set configured by
- SearchSpace
in PDCCH-Config with searchSpaceType = common for DCI
formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI,
TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or NES-RNTI
cellDTRX-RNTI
and, only for the primary cell, C-RNTI, MCS-C-RNTI, CS-RNTI(s), or PS-RNTI, or
<unchanged parts are omitted>
------------ end of TP for TS 38.213 -----------------------
Agreement
· Reason for change: The order of resolving overlapping PUCCH(s) and/or PUSCH(s) and performing cell DRX operation is not clear in spec.
· Summary of change: First resolving overlapping PUCCH(s) and/or PUSCH(s) and then performing cell DRX operation.
· Consequences if not approved: The order of resolving overlapping PUCCH(s) and/or PUSCH(s) and performing cell DRX operation is not defined in spec.
===== Start of TP for TS38.213 ======
9 UE procedure for reporting control information
*** Unchanged text is omitted ***
- else
- if the UE would transmit the following channels that would overlap in time where, if a channel transmission is with repetitions, the following are applicable per repetition
- a first PUCCH transmission of larger priority index and a second PUCCH transmission of smaller priority index
- a first PUCCH transmission of larger priority index and a second PUSCH transmission of smaller priority index when the UE cannot simultaneously transmit the first PUCCH and second PUSCH
- a first PUCCH transmission of smaller priority index and a second PUSCH transmission of larger priority index when the UE cannot simultaneously transmit the first PUCCH and second PUSCH
the UE
- transmits the PUCCH or the PUSCH of the larger priority index subject to the limitations for UE transmissions due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, and 15 and
- does not transmit a PUCCH or a PUSCH of smaller priority index
*** Unchanged text is omitted ***
===== End of TP for TS38.213 =======
Agreement
Include cellDTXDRX-L1activation to the updated RRC parameter list to be shared with RAN2.
· Description for parameter: Configure L1 signaling based on DCI 2_9 to enable dynamic activation/deactivation of cell DTX/DRX configuration per serving cell. Note: cellDTXDRX-L1activation can be configured individually per cell for subset of serving cells.
· Signaling to be provided per serving cell.
Agreement
· Reasons for change: It is already agreed the HARQ feedback of cancelled SPS PDSCH by non-active period of cell DTX is not transmitted by UE. But for Type 2 HARQ-ACK codebook for SPS PDSCHs, it is not differentiated SPS PDSCH with or without non-active period of cell DTX in the current specification.
· Summary of change: UE does not generate a HARQ-ACK information bit for an SPS PDSCH overlapping with non-active period of cell DTX for Type 2 HARQ-ACK codebook for SPS PDSCHs.
· Consequences if not adopted: Un-aligned UE behaviour for Type 1 and Type 2 HARQ-ACK codebook generation
========== Start of TP for TS38.213 ===========
9.1.3.1 Type-2 HARQ-ACK codebook in physical uplink control channel
*** Unchanged text omitted ***
If
a UE is
configured to receive SPS PDSCH and the UE multiplexes HARQ-ACK information
for one activated SPS PDSCH reception based on downlinkHARQ-FeedbackDisabled
if provided [12, TS 38.331], including the ones associated with the
corresponding activation DCI, in the PUCCH in slot 
, the UE
generates one
HARQ-ACK
information bit associated with the SPS PDSCH reception not overlapping with non-active period of cell DTX
of a serving cell, if cell DTX is activated for the serving cell
with the SPS PDSCH reception, and appends it to the 
HARQ-ACK
information bits.
If
a UE is configured to receive SPS PDSCH and the UE multiplexes HARQ-ACK
information for multiple activated SPS PDSCH receptions, including the ones
associated with the corresponding activation DCI and excluding the ones that
provide only transport blocks for HARQ processes associated with disabled
HARQ-ACK information if downlinkHARQ-FeedbackDisabled is provided, in the PUCCH
in slot , the UE
generates the HARQ-ACK information as described in clause 9.1.2 and appends it
to the HARQ-ACK
information bits.
*** Unchanged text omitted ***
========== End of TP for TS38.213 ============
Agreement
· Reason for change: The UE behavior is not defined for CSI-ReportConfig configured with time restriction set to "Configured", when cell DTX is activated on the serving cell with the CSI resource Setting linked to the CSI-ReportConfig.
· Summary of change: Defines the UE behavior for CSI-ReportConfig configured with time restriction set to "Configured", when cell DTX is activated on the serving cell with the CSI resource Setting linked to the CSI-ReportConfig.
· Consequences if not approved: Undefined UE behavior on performing CSI report corresponding to CSI-ReportConfig configured with time restriction, when cell DTX is activated on the serving cell with the CSI resource Setting linked to the CSI-ReportConfig.
|
5.2.2.1 Channel quality indicator (CQI) *** Unchanged text is omitted *** If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing CSI reported in uplink slot n based on only the most recent, no later than the CSI reference resource, in cell DTX active time of a serving cell if cell DTX is activated, occasion of NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting on the serving cell. *** Unchanged text is omitted *** If the higher layer parameter timeRestrictionForInterferenceMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the interference measurements for computing the CSI value reported in uplink slot n based on the most recent, no later than the CSI reference resource, in cell DTX active time of a serving cell if cell DTX is activated, occasion of CSI-IM and/or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) associated with the CSI resource setting on the serving cell. *** Unchanged text is omitted *** |
Agreement
· Reason for change: The UE behavior is not defined for CSI-ReportConfig configured with the higher layer parameter reportQuantity comprising at least 'RI', when cell DTX is activated on the serving cell for the corresponding measurement resource.
· Summary of change: Defines the UE behavior for CSI-ReportConfig configured with the higher layer parameter reportQuantity comprising at least 'RI', when cell DTX is activated on the serving cell for the corresponding measurement resource.
· Consequences if not approved: Undefined UE behavior on performing CSI report or receiving CSI-RS corresponding to CSI-ReportConfig configured with the higher layer parameter reportQuantity comprising at least 'RI', when cell DTX is activated on the serving cell for the corresponding measurement resource.
|
5.1.6.1 CSI-RS reception procedure *** Unchanged text is omitted *** During non-active
periods of cell DTX if cell DTX is activated
for a serving cell, the UE *** Unchanged text is omitted *** 5.2.2.5 CSI reference resource definition *** Unchanged text is omitted *** For the CSI
report configuration
in CSI-ReportConfig associated with the higher layer parameter reportQuantity
comprising at least 'RI' *** Unchanged text is omitted *** |
Agreement
· Reason for change: Ambiguous UE behavior is during resolution of the overlapping among PDSCHs (TS 38.214 clause 5) and determination of whether to receive a SPS PDSCH overlapping with non-active period of cell DTX.’
· Summary of change: the UE first performs determination of whether to receive a SPS PDSCH overlapping with non-active period of cell DTX and then performs resolution of the overlapping among PDSCHs (TS 38.214 clause 5.1).
· Consequences if not approved: Unclear UE behavior on which PDSCH should be received among the overlapping PDSCHs due to cell DTX operation
===== Start of TP for TS38.214 =======
5.1 UE procedure for receiving the physical downlink shared channel
*** Unchanged text is omitted ***
If more than one PDSCH on a serving cell each without a corresponding PDCCH transmission are in a slot, after resolving overlapping with symbols in the slot indicated as uplink by tdd-UL-DL-ConfigurationCommon, or by tdd-UL-DL-ConfigurationDedicated, or determined as non-active periods of cell DTX, if the serving cell is activated with cell DTX, based on [10, TS38.321], a UE receives one or more PDSCHs without corresponding PDCCH transmissions in the slot as specified below.
- Step 0: set j=0, where j is the number of selected PDSCH(s) for decoding. Q is the set of activated PDSCHs without corresponding PDCCH transmissions within the slot
- Step 1: A UE receives one PDSCH with the lowest configured sps-ConfigIndex within Q, set j=j+1. Designate the received PDSCH as survivor PDSCH.
- Step 2: The survivor PDSCH in step 1 and any other PDSCH(s) overlapping (even partially) with the survivor PDSCH in step 1 are excluded from Q.
- Step 3: Repeat step 1 and 2 until Q is empty or j is equal to the number of unicast/multicast PDSCHs in a slot supported by the UE
===== End of TP for TS38.214 =======
R1-2401751 Summary #3 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism Moderator (Intel Corporation)
Agreement
· Reasons for change: Unclear UE behaviour if a PUCCH with HARQ-ACK and CSI/SR overlaps with non-active period of cell DRX. Unclear UE behaviour if a PUSCH with HARQ-ACK overlaps with non-active period of cell DRX if the PUSCH is not associated with a corresponding PDCCH.
· Summary of change: UE drops the PUCCH without HARQ-ACK and drops the PUSCH without a corresponding PDCCH if HARQ-ACK is not multiplexed in the PUSCH if cell DRX is activated for a serving cell and the PUCCH or the PUSCH overlaps with the non-active period of the serving cell, respectively.
· Consequences if not adopted: Incomplete specification.
===== Start of TP for TS38.213 ======
9 UE procedure for reporting control information
*** Unchanged Text Omitted ***
When a UE determines overlapping for PUCCH and/or PUSCH transmissions of the same priority index other than PUCCH transmissions with SL HARQ-ACK reports before considering limitations for UE transmission due to cell DRX operation [11, TS 38.321] or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2 including repetitions if any,
- first, the UE resolves the overlapping for PUCCHs with repetitions as described in clause 9.2.6, if any
- second, the UE resolves the overlapping for PUCCHs without repetitions as described in clauses 9.2.5
- third, the UE resolves the overlapping for PUSCHs and PUCCHs with repetitions as described in clause 9.2.6
- fourth, the UE resolves the overlapping for PUSCHs and PUCCHs without repetitions as is subsequently described in this clause.
After resolving the overlapping for PUCCH and/or PUSCH transmissions and if cell DRX is activated for a serving cell and a PUCCH or PUSCH overlaps with the non-active period of cell DRX of the serving cell, the UE drops the PUCCH, if HARQ-ACK is not multiplexed in the PUCCH, or drops the PUSCH, if HARQ-ACK is not multiplexed in the PUSCH and the PUSCH is without a corresponding PDCCH, respectively.
If a UE
- is provided simultaneousPUCCH-PUSCH and would transmit a PUCCH with a first priority index and PUSCHs with a second priority index that is different than the first priority index, where the PUCCH and the PUSCHs overlap in time on different respective cells
- can simultaneously transmit the PUCCH and the PUSCHs with different priority indexes [18, TS 38.306],
the UE excludes the PUSCHs for resolving the time overlapping between the PUCCH and PUSCHs with different priority indexes, where the timeline conditions for resolving the overlapping PUCCH and PUSCHs are not required for the excluded PUSCHs.
===== End of TP for TS38.213 ======
Agreement
Agreement
Send LS to RAN2 to ask to capture the following RAN1 agreement and any additional RAN1 agreement regarding handling of repetition of PUCCH, PUSCH, and SPS PDSCH into RAN2 specification.
|
Agreement UE transmits a subset of the repetitions in a CG bundle that do not overlap with the cell DRX non-active period |
R1-2401753 Draft LS on Network Energy Savings Moderator (Intel Corporation, Huawei)
Decision: The draft LS is endorsed. Final LS is approved in R1-2401810.
Final summary in R1-2401752.
